Triple
T21453683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bodie Cemetery |
E529281
|
entity |
| Predicate | coordinateUncertainty |
P144409
|
FINISHED |
| Object | approximate |
—
|
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: approximate | Statement: [Bodie Cemetery, coordinateUncertainty, approximate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateUncertainty Context triple: [Bodie Cemetery, coordinateUncertainty, approximate]
-
A.
locatesUncertaintyIn
Indicates that one entity identifies or specifies the particular place, context, or aspect in which uncertainty is situated or attributed.
-
B.
coordinateMeasured
Indicates that a specific coordinate value has been determined or recorded for an entity.
-
C.
coordinates
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
-
D.
coordinatesDoctrineIn
Indicates that one entity organizes and aligns doctrinal matters or policies within a specified context, domain, or location.
-
E.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9d50b88819081a771596d0a2b2b |
completed | April 23, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e63d2aca38819094d312078feaa436 |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 16, 2026, 6:07 p.m.