Triple
T12790859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stevenage F.C. |
E305753
|
entity |
| Predicate | homeTownPopulation |
P38055
|
FINISHED |
| Object | around 90,000 |
—
|
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: around 90,000 | Statement: [Stevenage F.C., homeTownPopulation, around 90,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTownPopulation Context triple: [Stevenage F.C., homeTownPopulation, around 90,000]
-
A.
municipalityPopulation
chosen
Indicates the total number of inhabitants living within a given municipality.
-
B.
homeCityPopulationRegion
Indicates that the population of a home city falls within or is associated with a specified geographic region.
-
C.
hasPopulationLocation
Indicates that a population is located in or associated with a specific geographic place or area.
-
D.
metropolitanAreaPopulationApproximate
Indicates that the predicate specifies an approximate total population size for a given metropolitan area.
-
E.
cityPopulationContext
Indicates the contextual relationship between a city and information about its population, such as size, distribution, or demographic characteristics.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e6b55248190ab938e69eb263612 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:30 p.m.