Triple
T31308634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Webb, Mississippi |
E798400
|
entity |
| Predicate | hasPopulationCensus2000 |
P192868
|
FINISHED |
| Object | 587 |
—
|
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: 587 | Statement: [Webb, Mississippi, hasPopulationCensus2000, 587]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopulationCensus2000 Context triple: [Webb, Mississippi, hasPopulationCensus2000, 587]
-
A.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
B.
hasPopulationOf
Indicates that an entity possesses a specific number of inhabitants or residents as its population.
-
C.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
D.
populationCensusValue
chosen
Indicates the recorded number of individuals in a population as determined by an official census at a specific time and place.
-
E.
rankInUS2010Census
Indicates the numerical position of an entity in the ranking of occurrences within the 2010 United States Census.
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 29, 2026, 9:14 p.m.