Triple
T23738526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commerce, Illinois |
E586600
|
entity |
| Predicate | presentLocationNowCalled |
P58279
|
FINISHED |
| Object | Nauvoo, Illinois |
—
|
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: Nauvoo, Illinois | Statement: [Commerce, Illinois, presentLocationNowCalled, Nauvoo, Illinois]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentLocationNowCalled Context triple: [Commerce, Illinois, presentLocationNowCalled, Nauvoo, Illinois]
-
A.
locationNowCalled
chosen
Indicates that a location is currently known or referred to by a different (typically newer) name than it was previously.
-
B.
currentlyLocatedAt
Indicates that an entity’s present or most recent known physical location is at the specified place.
-
C.
presentDayLocationCorrespondsTo
Indicates that the current, real-world location of an entity matches or aligns with a specified reference location.
-
D.
locationPresented
Indicates that a specific location is presented or shown to an entity (such as a user or system) within a given context.
-
E.
currentLocationType
Indicates the type or category of place where an entity is currently located.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad427f081908eaf96273fec757b |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:11 p.m.