Triple
T33566882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American Datum of 1927 |
E859783
|
entity |
| Predicate | referencePointLocation |
P1573
|
FINISHED |
| Object | Kansas |
—
|
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: Kansas | Statement: [North American Datum of 1927, referencePointLocation, Kansas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referencePointLocation Context triple: [North American Datum of 1927, referencePointLocation, Kansas]
-
A.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
B.
coordinateLocation
chosen
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
C.
subjectLocation
Indicates that one entity is located at, in, or near the place or position specified by another entity.
-
D.
reportedLocation
Indicates that an entity has been specified or recorded as being at a particular location, typically based on a report or observation rather than direct verification.
-
E.
objectLocation
Indicates that one entity is located at, in, or on another entity or spatial region.
- 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: May 1, 2026, 1:40 a.m.