Triple
T29610135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 巴士海峽 |
E754691
|
entity |
| Predicate | 航運功能 |
P59758
|
FINISHED |
| Object | 連接東亞與東南亞航線 |
—
|
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: 連接東亞與東南亞航線 | Statement: [巴士海峽, 航運功能, 連接東亞與東南亞航線]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 航運功能 Context triple: [巴士海峽, 航運功能, 連接東亞與東南亞航線]
-
A.
maritimeFunction
chosen
Indicates a relationship where an entity serves a role, purpose, or operational function specifically within maritime contexts such as sea transport, navigation, or marine activities.
-
B.
shipFunction
Indicates that one entity serves as the functional role, purpose, or operational use of a ship.
-
C.
waterTransport
Indicates the movement or conveyance of something from one place to another via water-based means such as rivers, seas, or other aquatic routes.
-
D.
shipRig
Indicates that one entity is equipped with or configured using the rigging system specified by another entity.
-
E.
shipOperator
Indicates the entity that is responsible for operating, managing, or running a ship.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66dea375881909684db997861425c |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:28 p.m.