Triple
T34772234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empire Shackleton |
E1002393
|
entity |
| Predicate | routeRisk |
P181599
|
FINISHED |
| Object | dangerous sea routes |
—
|
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: dangerous sea routes | Statement: [SS Empire Shackleton, routeRisk, dangerous sea routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeRisk Context triple: [SS Empire Shackleton, routeRisk, dangerous sea routes]
-
A.
transportRisk
Indicates the level or type of potential loss, damage, or adverse outcome associated with transporting something from one place to another.
-
B.
roadMode
Indicates the mode or type of transportation being used on a road within the described relationship or action.
-
C.
roadAffected
Indicates that a road is impacted or disrupted by a condition, event, or action, such as construction, accidents, or adverse weather.
-
D.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
E.
withinDrivingRoute
Indicates that one location can be reached from another via a practical or allowable driving route, typically within a reasonable distance or time.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f77ff804f08190b431a31e6179ace4 |
completed | May 3, 2026, 5:03 p.m. |
Created at: May 3, 2026, 3:59 p.m.