Triple
T24149718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mindoro Strait |
E598493
|
entity |
| Predicate | isPartOfSeaRouteBetween |
P62174
|
FINISHED |
| Object | South China Sea |
—
|
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: South China Sea | Statement: [Mindoro Strait, isPartOfSeaRouteBetween, South China Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfSeaRouteBetween Context triple: [Mindoro Strait, isPartOfSeaRouteBetween, South China Sea]
-
A.
hasSeaRouteConnection
Indicates that there exists a navigable maritime route linking two locations or entities.
-
B.
associatedWithSeaRoute
chosen
Indicates a relationship where something is connected or related to a particular sea route, such as by use, location, or relevance.
-
C.
connectsInlandRoutesTo
Indicates that one entity serves as a link or junction that enables inland transportation routes to reach or connect with another entity.
-
D.
isPortOf
Indicates that one location or facility serves as a port or harbor for another place, entity, or transportation route.
-
E.
isOneOfMainCarFerryRoutesTo
Indicates that something serves as one of the primary car ferry routes leading to a specified destination.
- 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_69e288c9e488819093dd1acd91b08b8a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e00e025c81908cacfcfa0819c73f |
completed | April 29, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:30 p.m.