Triple
T34409873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auckland–Sydney |
E883225
|
entity |
| Predicate | regionDestination |
P83648
|
FINISHED |
| Object | New South Wales |
—
|
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 South Wales | Statement: [Auckland–Sydney, regionDestination, New South Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionDestination Context triple: [Auckland–Sydney, regionDestination, New South Wales]
-
A.
territoryOfDestination
Indicates that a specified territory is the destination or endpoint location associated with an action, movement, or relation.
-
B.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
C.
hasDestinationRegion
chosen
Indicates that something is directed, sent, or intended to arrive at a particular geographic or logical region as its destination.
-
D.
recipientRegion
Indicates the geographic region that receives or is the destination of a transfer, delivery, or directed action.
-
E.
regionOfHostCountry
Indicates that one entity is a geographic or administrative region belonging to, or located within, the specified host country.
- 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
Created at: May 1, 2026, 1:59 a.m.