Triple
T25863355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyneside |
E651543
|
entity |
| Predicate | populationRankInUKUrbanAreas |
P3423
|
FINISHED |
| Object | one of the largest |
—
|
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: one of the largest | Statement: [Tyneside, populationRankInUKUrbanAreas, one of the largest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: populationRankInUKUrbanAreas Context triple: [Tyneside, populationRankInUKUrbanAreas, one of the largest]
-
A.
hasPopulationRankInUK
chosen
Indicates the relative position of an entity’s population size compared to other entities within the United Kingdom.
-
B.
boroughPopulation
Indicates the total number of people living within a specific borough.
-
C.
significantUrbanArea
Indicates that a location is classified as a major or important urban center within a broader geographic or administrative context.
-
D.
areaRank
Indicates the relative ordering or position of an entity based on the size of its area compared to others.
-
E.
relatedUrbanArea
Indicates that one urban area is geographically or functionally associated with another urban area, such as being nearby, connected, or part of the same broader metropolitan context.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 22, 2026, 8:06 a.m.