Triple
T3552926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makassar Strait |
E75150
|
entity |
| Predicate | isRouteFor |
P50556
|
FINISHED |
| Object | LNG shipments |
—
|
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: LNG shipments | Statement: [Makassar Strait, isRouteFor, LNG shipments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRouteFor Context triple: [Makassar Strait, isRouteFor, LNG shipments]
-
A.
isMajorRouteFor
Indicates that something serves as a primary or heavily used pathway or channel for the movement or flow of something else.
-
B.
hasRoute
Indicates that there exists a path or connection enabling travel or communication from one entity to another.
-
C.
isStandardRouteOn
Indicates that a particular route is the default or officially designated path used on a given transportation line or service.
-
D.
isKeyRoute
Indicates that a route plays a primary or strategically important role within a network or system.
-
E.
isDestinationFor
Indicates that one entity serves as the endpoint or target location that another entity is intended to reach or be directed toward.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc05394888190b59fafda97b49beb |
completed | March 8, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69adb83270ac819083967db0570167d2 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adba25c66c81909a05a97327828c41 |
completed | March 8, 2026, 6:04 p.m. |
Created at: March 8, 2026, 3:20 p.m.