Triple
T35855097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evergreen Cemetery, Los Angeles |
E1036478
|
entity |
| Predicate | hasNotableIntermentType |
P3803
|
FINISHED |
| Object | pioneers of Los Angeles |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: pioneers of Los Angeles | Statement: [Evergreen Cemetery, Los Angeles, hasNotableIntermentType, pioneers of Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableIntermentType Context triple: [Evergreen Cemetery, Los Angeles, hasNotableIntermentType, pioneers of Los Angeles]
-
A.
hasTypeOfBurial
Indicates the specific kind or method of burial associated with an entity.
-
B.
hasNotableBurials
chosen
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
C.
hasBurialRestriction
Indicates that there is a rule, condition, or limitation governing how, where, or whether a burial may take place.
-
D.
hasBurialCustoms
Indicates that a group, culture, or society practices specific rituals or customs related to the treatment and burial of the dead.
-
E.
containsHeartBurial
Indicates that one entity includes or features the burial of a heart within it.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e1b4aa481909630373171eb5ec6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.