Triple
T31451502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miriam A. Ferguson cenotaph |
E802331
|
entity |
| Predicate | isInCemeterySection |
P3802
|
FINISHED |
| Object | Texas State Cemetery gubernatorial section |
—
|
NE NERFINISHED |
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: Texas State Cemetery gubernatorial section | Statement: [Miriam A. Ferguson cenotaph, isInCemeterySection, Texas State Cemetery gubernatorial section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInCemeterySection Context triple: [Miriam A. Ferguson cenotaph, isInCemeterySection, Texas State Cemetery gubernatorial section]
-
A.
isCemeteryFor
Indicates that one entity serves as the burial ground designated for another entity, such as a community, group, or location.
-
B.
cemeterySection
Indicates that one entity is a specific section, area, or subdivision within a cemetery associated with the other entity.
-
C.
locatedInCemetery
chosen
Indicates that one entity is situated within the grounds or area of a cemetery.
-
D.
isInHistoricCemetery
Indicates that an entity is located within a cemetery that is recognized as historic.
-
E.
hasCemetery
Indicates that one entity possesses, contains, or includes a cemetery associated with 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_69f348c678ac81908a2e950867619061 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:13 p.m.