Triple
T32094233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Zealand Schools |
E819683
|
entity |
| Predicate | notablePathwayTo |
P43975
|
FINISHED |
| Object | New Zealand Under-20 rugby union team |
E853838
|
NE 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: New Zealand Under-20 rugby union team | Statement: [New Zealand Schools, notablePathwayTo, New Zealand Under-20 rugby union team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePathwayTo Context triple: [New Zealand Schools, notablePathwayTo, New Zealand Under-20 rugby union team]
-
A.
notableRouteType
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
-
B.
hasNotableConnectionTo
chosen
Indicates a significant or noteworthy relationship, association, or link exists between two entities.
-
C.
notableCycle
Indicates that there is a particularly significant or noteworthy recurring sequence or cycle involving the related entities.
-
D.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
E.
routeOf
Indicates that one entity is the path, course, or trajectory taken or followed by another entity (such as a vehicle, shipment, or signal).
- F. None of above.
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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f0bbf0a10819089531023f477ff3f |
completed | June 14, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:25 a.m.