Triple
T6221526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hibernia |
E139124
|
entity |
| Predicate | hasExportMethod |
P68049
|
FINISHED |
| Object | shuttle tankers |
—
|
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: shuttle tankers | Statement: [Hibernia, hasExportMethod, shuttle tankers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExportMethod Context triple: [Hibernia, hasExportMethod, shuttle tankers]
-
A.
isExportable
Indicates that something can be legally and practically transferred or sent out from one jurisdiction, system, or context to another.
-
B.
hasMainExport
Indicates that one entity is the primary good or commodity exported by another entity.
-
C.
hasAccessMethod
Indicates that one entity uses or is associated with a particular method or mechanism for accessing another entity or resource.
-
D.
hasWorkingMethod
Indicates that one entity possesses or employs a functional method, procedure, or technique to achieve a particular task or outcome.
-
E.
handlesExport
chosen
Indicates that an entity is responsible for managing or processing the export of goods, data, or resources from one context or location to another.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062bcc2348190806ed8c98bdfbf3e |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.