Triple
T6757586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Busan waterfront |
E154500
|
entity |
| Predicate | cityRankContext |
P69297
|
FINISHED |
| Object | second-largest city in South Korea |
—
|
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: second-largest city in South Korea | Statement: [Busan waterfront, cityRankContext, second-largest city in South Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityRankContext Context triple: [Busan waterfront, cityRankContext, second-largest city in South Korea]
-
A.
areaRank
Indicates the relative ordering or position of an entity based on the size of its area compared to others.
-
B.
hasCityRank
chosen
Indicates that a city holds a particular rank or position within a defined ordering or hierarchy (such as size, importance, or administrative level).
-
C.
populationRank
Indicates the relative position of an entity in an ordered list based on the size of its population.
-
D.
isGlobalCityRank
Indicates the relative position or ranking of a city within a global hierarchy of cities based on specified criteria.
-
E.
citySigned
Indicates that a city has formally signed or endorsed an agreement, document, or commitment.
- 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_69c6880fd5808190be684854081e27dd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d327e37081909d576e6eff9eec97 |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09227108190b253b91967831a85 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:11 p.m.