Triple
T1351704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulsan |
E28895
|
entity |
| Predicate | wasUpgradedToMetropolitanCityIn |
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, wasUpgradedToMetropolitanCityIn, 1997]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUpgradedToMetropolitanCityIn Context triple: [Ulsan, wasUpgradedToMetropolitanCityIn, 1997]
-
A.
incorporatedAsCity
Indicates that an entity was formally established and legally recognized as a city.
-
B.
hasMetropolitan
Indicates that an entity is associated with, served by, or located within a specific metropolitan area.
-
C.
hasMetropolitanAuthorityOver
Indicates that one entity holds official governing or administrative authority over a metropolitan area or region associated with another entity.
-
D.
isMetropolitanCoreOf
Indicates that one area functions as the central, most urbanized core within a larger metropolitan region or system.
-
E.
metropolitanStatusHeld
Indicates that an entity holds or is assigned a particular metropolitan status (e.g., being designated as part of a metropolitan area or category).
- F. None of above. chosen
Provenance (4 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c26b1b4881908ae4b1b2c9b268a0 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bf60545c8190901ccfb2cb7c4b41 |
completed | March 1, 2026, 10:36 p.m. |
Created at: March 1, 2026, 7:56 p.m.