Triple
T29610132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 巴士海峽 |
E754691
|
entity |
| Predicate | 最窄寬度 |
P126281
|
FINISHED |
| Object | 約80公里 |
—
|
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: 約80公里 | Statement: [巴士海峽, 最窄寬度, 約80公里]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 最窄寬度 Context triple: [巴士海峽, 最窄寬度, 約80公里]
-
A.
isNarrowestPartOf
Indicates that one entity constitutes the slimmest or most constricted section within the extent or structure of another entity.
-
B.
hasNarrowestWidth
chosen
Indicates that one entity has the smallest width dimension compared to a specified set of entities or alternatives.
-
C.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
-
D.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
-
E.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
- 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.