Triple
T27411697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moonbae-dong |
E692168
|
entity |
| Predicate | coastalCityNeighborhood |
P100195
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Moonbae-dong, coastalCityNeighborhood, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coastalCityNeighborhood Context triple: [Moonbae-dong, coastalCityNeighborhood, true]
-
A.
isCoastalCityNeighbourhood
chosen
Indicates that a neighborhood is located within a city that lies along a sea, ocean, or other significant coastal body of water.
-
B.
isCoastalCitySuburb
Indicates that a suburb is located within or adjacent to a city that lies on a coastline, functioning as a suburban area of that coastal city.
-
C.
typicalNeighborhoods
Indicates that the associated neighborhoods are characteristic or commonly found examples for the given entity or context.
-
D.
neighborhood
Indicates that one entity is located in close spatial proximity to another, typically within the same local area or district.
-
E.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cdb62608190a8e1c84a631de5ce |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:32 p.m.