Triple
T29610130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 巴士海峽 |
E754691
|
entity |
| Predicate | 所屬國家附近 |
P135404
|
FINISHED |
| Object | 中華民國（台灣） |
—
|
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: 中華民國（台灣） | Statement: [巴士海峽, 所屬國家附近, 中華民國（台灣）]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 所屬國家附近 Context triple: [巴士海峽, 所屬國家附近, 中華民國（台灣）]
-
A.
locatedNearCountry
chosen
Indicates that one entity is geographically situated close to the borders or territory of a specified country.
-
B.
countryWhoseCoastItWasNear
Indicates that one entity is a country and the other is a coastal feature or location situated near that country’s coastline.
-
C.
geographicallyAdjacentTo
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
D.
nearFirstNationsTerritory
Indicates that one entity is located close to, but not necessarily within, the territory traditionally or legally associated with a First Nations group.
-
E.
hasNearbyPortCountry
Indicates that one entity is a country that has a seaport located geographically close to the other entity.
- 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.