Triple
T36628006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mustang |
E904227
|
entity |
| Predicate | notablePopulationRegion |
P204977
|
FINISHED |
| Object | Nevada |
E2834
|
NE 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: Nevada | Statement: [Mustang, notablePopulationRegion, Nevada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePopulationRegion Context triple: [Mustang, notablePopulationRegion, Nevada]
-
A.
notablePopulationCenter
Indicates that a location is recognized as a significant or prominent center of population within a given area or context.
-
B.
hasPopulationInRegion
Indicates that a specified population quantity is associated with, or resides within, a particular geographic or administrative region.
-
C.
hasNotablePopulation
Indicates that an entity is recognized for having a significant or noteworthy number of inhabitants or members.
-
D.
populationRegion
Indicates that a specified population is located within or associated with a particular geographic region.
-
E.
hasPopulationNote
Indicates that there is a special remark, qualifier, or explanatory note associated with the population value of an entity.
- F. None of above. chosen
Provenance (5 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a09668388819085038ba372ba1ce8 |
completed | June 23, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82f8c88190bd77a086023ac0e1 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:11 p.m.