Triple
T11771486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Campus |
E279908
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Songdo-dong |
E637403
|
NE 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: Songdo-dong | Statement: [International Campus, locatedIn, Songdo-dong]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Songdo-dong Context triple: [International Campus, locatedIn, Songdo-dong]
-
A.
Songdo-dong
chosen
Songdo-dong is a modern waterfront neighborhood in Incheon, South Korea, best known for hosting the high-tech, master-planned Songdo International Business District.
-
B.
Gocheon-dong
Gocheon-dong is a neighborhood (dong) that forms part of the city of Osan in Gyeonggi Province, South Korea.
-
C.
Okryeon-dong
Okryeon-dong is a neighborhood located within Yeonsu District in Incheon, South Korea.
-
D.
Jeungsan-dong
Jeungsan-dong is a neighborhood (dong) located within Pusanjin District in Busan, South Korea.
-
E.
Yangjeong-dong
Yangjeong-dong is a neighborhood (dong) located within Busanjin District in the city of Busan, South Korea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a55c9f988190b203b66a28c767ae |
completed | April 10, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f63477e08190957dd1ef709fe93b |
completed | May 2, 2026, 1:03 p.m. |
Created at: April 8, 2026, 9:41 p.m.