Triple
T13235237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sterling μSA |
E315129
|
entity |
| Predicate | urbanCorePopulationRange |
P28398
|
FINISHED |
| Object | 10,000 to 49,999 |
—
|
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: 10,000 to 49,999 | Statement: [Sterling μSA, urbanCorePopulationRange, 10,000 to 49,999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanCorePopulationRange Context triple: [Sterling μSA, urbanCorePopulationRange, 10,000 to 49,999]
-
A.
populationRange
chosen
Indicates the numerical interval within which the size of a population falls.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
peakPopulationApproximate
Indicates that the peak population of an entity is known only approximately rather than as an exact value.
-
D.
populationClass
Indicates a categorical classification of a population based on shared characteristics, status, or demographic criteria.
-
E.
ageRangeUpper
Indicates the maximum age limit that bounds the upper end of an age range associated with an entity or relationship.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d36bdf8819099949b1e0e6902d3 |
completed | April 10, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69d98bcb21648190aef241de1e7887e2 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:22 p.m.