Triple
T5294396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean King Sejong Station |
E119817
|
entity |
| Predicate | summerPopulationApprox |
P8162
|
FINISHED |
| Object | 60 |
—
|
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: 60 | Statement: [Korean King Sejong Station, summerPopulationApprox, 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summerPopulationApprox Context triple: [Korean King Sejong Station, summerPopulationApprox, 60]
-
A.
seasonalPopulation
chosen
Indicates a relationship where the number of individuals in a population varies depending on the season or time of year.
-
B.
currentPopulation
Indicates the present number of individuals living in or belonging to a specified entity (such as a location or group).
-
C.
hasPopulationApproximate
Indicates that an entity has an estimated or approximate population size, rather than an exact count.
-
D.
permanentPopulation
Indicates that an entity has a stable, long-term resident population rather than a temporary or transient presence.
-
E.
hasPopulationAsOf
Indicates that a population count is associated with a specific point or date in time when that population figure was valid or recorded.
- 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_69bd446f22b88190b6a47fb91c68a3e7 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.