Triple
T3836995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Auckland |
E91155
|
entity |
| Predicate | isLargestPortBy |
P33052
|
FINISHED |
| Object | container throughput in New Zealand |
—
|
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: container throughput in New Zealand | Statement: [Port of Auckland, isLargestPortBy, container throughput in New Zealand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLargestPortBy Context triple: [Port of Auckland, isLargestPortBy, container throughput in New Zealand]
-
A.
isLargestOf
Indicates that one entity has the greatest size, extent, or magnitude among a specified set of entities.
-
B.
hasMajorPort
Indicates that a location possesses a primary, significant seaport used for major commercial or transportation activities.
-
C.
isAmongLargestPortsIn
Indicates that a port ranks among the largest ports within a specified geographic or administrative area.
-
D.
isLargestSeaportIn
chosen
Indicates that one location is the largest seaport within a specified geographic or political region.
-
E.
isLargestTypeOf
Indicates that one entity represents the largest variant, category, or instance within a specified type or group relative to others.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb9baa508190800e73bf186f046e |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.