Triple
T6774655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulsan-gwangyeoksi |
E155125
|
entity |
| Predicate | elevatedToMetropolitanCity |
P26895
|
FINISHED |
| Object | 1997 |
—
|
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: 1997 | Statement: [Ulsan-gwangyeoksi, elevatedToMetropolitanCity, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: elevatedToMetropolitanCity Context triple: [Ulsan-gwangyeoksi, elevatedToMetropolitanCity, 1997]
-
A.
wasUpgradedToMetropolitanCityIn
chosen
Indicates that a city or town was officially elevated in status to a metropolitan city in a specified year or on a specific date.
-
B.
elevatedToMetropolitanArchdiocese
Indicates that a diocese or archdiocese has been formally raised in status to become a metropolitan archdiocese, typically gaining jurisdictional primacy over a group of suffragan dioceses.
-
C.
hasMetropolitan
Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
-
D.
metropolitan
Indicates that a location is part of, belongs to, or lies within a specified metropolitan (urban) area.
-
E.
isMetropolitanCoreOf
Indicates that one area functions as the central, most urbanized core within a larger metropolitan region or system.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24ddaf08190baffbff991eeb458 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.