Triple
T32112507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whanganui Journey |
E820153
|
entity |
| Predicate | hasAlternativeEndPoint |
P191021
|
FINISHED |
| Object | Whakahoro |
—
|
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: Whakahoro | Statement: [Whanganui Journey, hasAlternativeEndPoint, Whakahoro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeEndPoint Context triple: [Whanganui Journey, hasAlternativeEndPoint, Whakahoro]
-
A.
hasAlternativeStartingPoint
Indicates that something can begin from a different or optional initial point instead of the primary starting point.
-
B.
hasAlternativeAccess
Indicates that an entity can be reached, used, or obtained through one or more substitute or backup means in addition to the primary method.
-
C.
hasAlternativeService
Indicates that one service can be substituted or used in place of another as an alternative option.
-
D.
hasAlternativeBearers
Indicates that an entity can be carried, represented, or borne by more than one possible bearer or carrier as alternatives.
-
E.
hasAlternativeProfile
Indicates that an entity is associated with another profile that serves as an alternative or secondary representation of it.
- F. None of above. chosen
Provenance (4 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: May 1, 2026, 12:27 a.m.