Triple
T1427705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyre |
E30369
|
entity |
| Predicate | modernPopulationApprox |
P3412
|
FINISHED |
| Object | over 100000 inhabitants |
—
|
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: over 100000 inhabitants | Statement: [Tyre, modernPopulationApprox, over 100000 inhabitants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernPopulationApprox Context triple: [Tyre, modernPopulationApprox, over 100000 inhabitants]
-
A.
hasPopulationApproximate
chosen
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
B.
currentPopulation
Indicates the present number of individuals living in or belonging to a specified entity (such as a location or group).
-
C.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
-
D.
formerPopulation
Indicates that an entity once had a certain population value or size during a past time period but no longer does.
-
E.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c52e4ed881908d85e0cb9fe851ac |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c4752abc8190a33b634c4d6fad28 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.