Triple
T27524031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan–South Korea |
E694786
|
entity |
| Predicate | hasProposedLink |
P195806
|
FINISHED |
| Object | Japan–Korea Undersea Tunnel |
—
|
NE NERFINISHED |
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: Japan–Korea Undersea Tunnel | Statement: [Japan–South Korea, hasProposedLink, Japan–Korea Undersea Tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProposedLink Context triple: [Japan–South Korea, hasProposedLink, Japan–Korea Undersea Tunnel]
-
A.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
-
B.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
-
C.
hasBridgeProposal
Indicates that there is a proposed plan or suggestion to build or establish a bridge between the related entities.
-
D.
hasBeenLinkedTo
Indicates that an entity has been associated or connected with another entity, often suggesting a reported or inferred relationship between them.
-
E.
hasProposedRole
Indicates that one entity has suggested or put forward a specific role or position for another entity.
- 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_69ef538550208190aa9de8e2cb260d93 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: April 27, 2026, 1:22 p.m.