Triple
T4627197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanmon Straits |
E101126
|
entity |
| Predicate | hasMajorBridgeOpeningYear |
P47616
|
FINISHED |
| Object | 1973 (Kanmon Bridge) |
—
|
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: 1973 (Kanmon Bridge) | Statement: [Kanmon Straits, hasMajorBridgeOpeningYear, 1973 (Kanmon Bridge)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorBridgeOpeningYear Context triple: [Kanmon Straits, hasMajorBridgeOpeningYear, 1973 (Kanmon Bridge)]
-
A.
hasMajorBridge
Indicates that one entity possesses or includes a primary or significant bridge associated with it.
-
B.
originalBridgeOpened
Indicates that the first or initial version of a bridge was opened for use or put into operation.
-
C.
bridgeOpened
chosen
Indicates that a bridge has transitioned from a closed or inactive state to being open and available for use.
-
D.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
-
E.
hasBridgeTunnel
Indicates that there exists a bridge or tunnel connection between two locations or structures.
- 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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a2e9780819081add547c760abc9 |
completed | March 20, 2026, 2:31 p.m. |
| PD | Predicate disambiguation | batch_69bd5231db7c8190b38d4fdbad8bf842 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.