Triple
T2080684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morton Cemetery, Richmond, Texas |
E45231
|
entity |
| Predicate | hasTypeOfPlace |
P16688
|
FINISHED |
| Object | graveyard |
—
|
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: graveyard | Statement: [Morton Cemetery, Richmond, Texas, hasTypeOfPlace, graveyard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfPlace Context triple: [Morton Cemetery, Richmond, Texas, hasTypeOfPlace, graveyard]
-
A.
placeType
chosen
Indicates the type or category of place associated with an entity (e.g., city, park, building).
-
B.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
C.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
D.
hasMunicipalityType
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
E.
hasMainLocationType
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba345be48190a1895f388e7749e5 |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:41 p.m.