Triple
T1041006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission Santa Barbara |
E22468
|
entity |
| Predicate | cemeteryContains |
P1496
|
FINISHED |
| Object | graves of early settlers and Native Americans |
—
|
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: graves of early settlers and Native Americans | Statement: [Mission Santa Barbara, cemeteryContains, graves of early settlers and Native Americans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cemeteryContains Context triple: [Mission Santa Barbara, cemeteryContains, graves of early settlers and Native Americans]
-
A.
hasCemetery
chosen
Indicates that one entity possesses, contains, or includes a cemetery associated with it.
-
B.
locatedInCemetery
Indicates that one entity is situated within the grounds or area of a cemetery.
-
C.
burialPlace
Indicates the location where a person or entity is buried.
-
D.
cemeteryType
Indicates the specific kind or classification of a cemetery associated with an entity.
-
E.
burialCoordinates
Indicates the geographic location where an entity is buried, typically expressed as spatial coordinates.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b845fa8c8190a7b69629883b62e2 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.