Triple
T6089389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Townsville |
E135722
|
entity |
| Predicate | handlesImport |
P28567
|
FINISHED |
| Object | fuel |
—
|
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: fuel | Statement: [Port of Townsville, handlesImport, fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesImport Context triple: [Port of Townsville, handlesImport, fuel]
-
A.
handlesMajorityOfImportsFor
Indicates that one entity is responsible for managing or processing most of the import volume associated with another entity.
-
B.
importedWith
Indicates that one entity was brought into a system, context, or location together with or as part of another entity during an import process.
-
C.
imported
Indicates that something was brought into a country, system, or context from an external source.
-
D.
importedGeneration
Indicates that electrical energy was generated outside the local system or region and brought in for use through imports.
-
E.
handlesMaterial
chosen
Indicates that an entity is responsible for managing, processing, or otherwise dealing with a specified material.
- 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_69c0087bcc788190b20f093d3a6c60ec |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c057a862c88190912a913973c6b6fc |
completed | March 22, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69c049f3b1ec8190bea67a7bec6442a5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:12 p.m.