Triple
T24346033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Queensland Bulk Ports Corporation |
E613641
|
entity |
| Predicate | portTypeFocus |
P17285
|
FINISHED |
| Object | bulk ports |
—
|
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: bulk ports | Statement: [North Queensland Bulk Ports Corporation, portTypeFocus, bulk ports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portTypeFocus Context triple: [North Queensland Bulk Ports Corporation, portTypeFocus, bulk ports]
-
A.
focusType
Indicates the specific kind or category of focus or attention that is being applied to or associated with an entity or interaction.
-
B.
focusOf
Indicates that one entity is the primary subject, target, or center of attention, activity, or interest for another entity.
-
C.
portFunction
chosen
Indicates the specific operational role or purpose that a port serves within a system or network.
-
D.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
-
E.
portActivity
Indicates the level or type of operational activity occurring at a port, such as ship movements, cargo handling, or related maritime operations.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932978b88190afc441a3d4805e5f |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:58 a.m.