Triple
T5439317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castledawson |
E122091
|
entity |
| Predicate | hasPopulationCensus2011 |
P3412
|
FINISHED |
| Object | approximately 3000 |
—
|
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: approximately 3000 | Statement: [Castledawson, hasPopulationCensus2011, approximately 3000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopulationCensus2011 Context triple: [Castledawson, hasPopulationCensus2011, approximately 3000]
-
A.
populationCensus2021
Indicates that a population count or demographic data is recorded as part of the 2021 census.
-
B.
populationCensusAuthority
Indicates that an entity serves as the official authority responsible for conducting and overseeing population censuses for a given jurisdiction.
-
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.
hasPopulationApproximate
chosen
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
E.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
- 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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.