Triple
T13739336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond Bridge |
E330038
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Gwangandaegyo |
E180482
|
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: Gwangandaegyo | Statement: [Diamond Bridge, alsoKnownAs, Gwangandaegyo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gwangandaegyo Context triple: [Diamond Bridge, alsoKnownAs, Gwangandaegyo]
-
A.
Gwangandaegyo
chosen
Gwangandaegyo is a prominent suspension bridge in Busan, South Korea, known for its scenic coastal views and nighttime LED light displays.
-
B.
Yeongdodaegyo
Yeongdodaegyo is a bascule bridge in Busan, South Korea, known as the city’s first mainland–island bridge and a local historical landmark.
-
C.
Aegukga
Aegukga is the national anthem of South Korea, expressing patriotic devotion and love for the country.
-
D.
Gwanaksan
Gwanaksan is a prominent mountain in the Seoul metropolitan area of South Korea, known for its hiking trails, rocky peaks, and scenic views over the surrounding cities.
-
E.
Hwangje
Hwangje is the Korean imperial title corresponding to the Chinese sovereign known as the Yellow Emperor (Huangdi).
- 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0204d50c8190a5413cc9a1b26e14 |
completed | April 14, 2026, 8:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d6bce9881909209231f6dfcf9bf |
completed | May 3, 2026, 7:09 p.m. |
Created at: April 9, 2026, 9:55 p.m.