Triple
T30191333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garrison Creek |
E767493
|
entity |
| Predicate | buriedDuring |
P168524
|
FINISHED |
| Object | late 19th century |
—
|
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: late 19th century | Statement: [Garrison Creek, buriedDuring, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: buriedDuring Context triple: [Garrison Creek, buriedDuring, late 19th century]
-
A.
buriedFor
Indicates that one entity is buried on behalf of, in honor of, or as a memorial for another entity.
-
B.
buriedAs
Indicates that one entity is interred or laid to rest in the manner, role, or context specified by another entity.
-
C.
buriedUnder
Indicates that one entity is located beneath another entity in such a way that it is covered or concealed by it, as if buried.
-
D.
buriedWith
Indicates that one entity is interred in the same grave, tomb, or burial site as another entity.
-
E.
isBuriedIn
Indicates that one entity is located beneath the ground or enclosed within another entity, typically as in a grave, tomb, or burial site.
- F. None of above. chosen
Provenance (4 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67f84b03c8190a2574fde91d86e8c |
completed | May 2, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:28 p.m.