Triple
T26398120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Tasman football rivalry |
E663625
|
entity |
| Predicate | typicalTravelRoute |
P79601
|
FINISHED |
| Object | across the Tasman Sea |
—
|
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: across the Tasman Sea | Statement: [Trans-Tasman football rivalry, typicalTravelRoute, across the Tasman Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTravelRoute Context triple: [Trans-Tasman football rivalry, typicalTravelRoute, across the Tasman Sea]
-
A.
travelRouteOf
chosen
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
B.
travelRouteContext
Indicates the contextual details (such as purpose, conditions, or circumstances) under which a particular travel route is taken or defined.
-
C.
popularRouteVia
Indicates that a route between two locations commonly or frequently passes through a specified intermediate point or path.
-
D.
popularRouteTo
Indicates that one location is widely used or frequently chosen as a route or way to reach another location.
-
E.
popularRouteOn
Indicates that a particular route is frequently used or favored on a given transportation line, service, or network.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fea5e828cc8190a9b755a645dc56d2 |
completed | May 9, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69fea36443f08190b2aced9b4a0525fd |
completed | May 9, 2026, 3 a.m. |
Created at: April 26, 2026, 11:30 p.m.