Triple
T16230469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smithville |
E393964
|
entity |
| Predicate | formerNameStatus |
P65
|
FINISHED |
| Object | no longer in official use |
—
|
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: no longer in official use | Statement: [Smithville, formerNameStatus, no longer in official use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameStatus Context triple: [Smithville, formerNameStatus, no longer in official use]
-
A.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
B.
formerMemberName
Indicates that the referenced name belongs to an entity that was previously a member of a particular group, organization, or body but is no longer one.
-
C.
heldAtFormerName
Indicates that an event or activity took place at a location when it was known by a previous or former name.
-
D.
previousNameUsedUntil
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
E.
nameRetiredFrom
Indicates that an entity has ceased holding or performing a particular named role, position, or activity.
- 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_69d87f204df88190a8f88923decf9835 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e23d29438c81909aa2724cc47bb959 |
completed | April 17, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.