Triple
T6802776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Busan urban area |
E156224
|
entity |
| Predicate | urbanCoreType |
P31474
|
FINISHED |
| Object | coastal city |
—
|
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: coastal city | Statement: [Greater Busan urban area, urbanCoreType, coastal city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanCoreType Context triple: [Greater Busan urban area, urbanCoreType, coastal city]
-
A.
isUrbanForm
Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
-
B.
garmentType
Indicates the specific kind or category of garment associated with an entity.
-
C.
fashionStyle
Indicates the characteristic way in which an entity dresses or presents themselves in terms of clothing and appearance.
-
D.
fashionCharacteristic
Indicates a relationship where one entity possesses or exhibits a particular style, trend, or fashion-related attribute in relation to another.
-
E.
urbanDistrictType
chosen
Indicates the classification of an urban district according to its specific type or category within an administrative or planning 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_69c68826e6a48190a3d220b541e639de |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2e714d4819084c8109c4de7de72 |
completed | March 27, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69c6d099bf08819089a9f9894d037e74 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.