Triple
T34625131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tāmaki River |
E889115
|
entity |
| Predicate | connectedByPortageTo |
P129035
|
FINISHED |
| Object | Manukau Harbour |
—
|
NE NERFINISHED |
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: Manukau Harbour | Statement: [Tāmaki River, connectedByPortageTo, Manukau Harbour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedByPortageTo Context triple: [Tāmaki River, connectedByPortageTo, Manukau Harbour]
-
A.
connectedViaPortageTo
chosen
Indicates that two locations are linked by a portage route, requiring overland transport between navigable waterways.
-
B.
hasMajorPortage
Indicates that one location serves as a primary or significant portage route for another location or waterway.
-
C.
associatedWithPorts
Indicates that there is a connection or involvement between an entity and one or more ports, such as using, serving, or being linked to those ports.
-
D.
relatedPortCluster
Indicates that one port cluster is associated with or connected to another port cluster in a relevant operational or logical way.
-
E.
linkedToPort
Indicates that one entity is connected or associated with a specific port, such as a network, hardware, or interface port.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 1, 2026, 2:04 a.m.