Triple
T24285857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeongdodaegyo |
E605666
|
entity |
| Predicate | bridgeLiftUsedFor |
P155695
|
FINISHED |
| Object | ceremonial and touristic purposes |
—
|
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: ceremonial and touristic purposes | Statement: [Yeongdodaegyo, bridgeLiftUsedFor, ceremonial and touristic purposes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bridgeLiftUsedFor Context triple: [Yeongdodaegyo, bridgeLiftUsedFor, ceremonial and touristic purposes]
-
A.
bridgeUsed
Indicates that a bridge is utilized or traversed by an entity to cross between two locations or points.
-
B.
bridgeFeature
Indicates that one entity functions as a structural or functional feature of a bridge associated with another entity.
-
C.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
D.
hasSwingBridge
Indicates that one entity possesses or includes a swing bridge, i.e., a bridge section that can pivot or rotate to allow passage (typically of water traffic).
-
E.
rebuiltAsLiftBridge
Indicates that an existing structure was reconstructed or converted into a lift bridge.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5605f081908367bd08ab1ec9ab |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:08 a.m.