Triple
T858318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nashville |
E18543
|
entity |
| Predicate | populationRankInTennessee |
P20240
|
FINISHED |
| Object | largest city in Tennessee |
—
|
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: largest city in Tennessee | Statement: [Nashville, populationRankInTennessee, largest city in Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationRankInTennessee Context triple: [Nashville, populationRankInTennessee, largest city in Tennessee]
-
A.
populationRankInTexas
Indicates the relative position of an entity in terms of population size compared to other entities within Texas.
-
B.
populationRankInMissouri
Indicates the relative position of an entity in terms of population size compared to other entities within the state of Missouri.
-
C.
populationRankInOhio
Indicates the relative ranking of an entity’s population size compared to other entities within the state of Ohio.
-
D.
areaRankInUS
Indicates the relative position of an entity in a ranking of areas within the United States, based on its size.
-
E.
rankByPopulationInUnitedStates
Indicates the relative ordering of entities based on their population size within the United States.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac4f740881909cb59a6c18a77af3 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.