Triple
T26134984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waitangi Wharf |
E659352
|
entity |
| Predicate | isRemoteRelativeTo |
P7317
|
FINISHED |
| Object | New Zealand mainland |
—
|
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: New Zealand mainland | Statement: [Waitangi Wharf, isRemoteRelativeTo, New Zealand mainland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRemoteRelativeTo Context triple: [Waitangi Wharf, isRemoteRelativeTo, New Zealand mainland]
-
A.
isRelativeTo
Indicates that one entity has a familial or kinship relationship to another entity.
-
B.
isMoreRemoteThan
Indicates that one entity is located at a greater distance or in a more out-of-the-way location compared to another entity.
-
C.
isRelatively
Indicates that one entity is being described, measured, or evaluated in relation to another entity or reference point, rather than in absolute terms.
-
D.
hasRelativeLocation
chosen
Indicates that one entity is positioned in space in relation to another entity’s location.
-
E.
isRemoteInParts
Indicates that the relationship or action occurs only in certain segments or portions of a larger whole, rather than being uniformly present throughout.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60b96085c81908a43574f4e07e70d |
completed | May 2, 2026, 2:35 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:17 p.m.