Triple
T34409872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auckland–Sydney |
E883225
|
entity |
| Predicate | regionOrigin |
P100363
|
FINISHED |
| Object | Auckland Region |
—
|
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: Auckland Region | Statement: [Auckland–Sydney, regionOrigin, Auckland Region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOrigin Context triple: [Auckland–Sydney, regionOrigin, Auckland Region]
-
A.
administrativeRegionOfOrigin
Indicates the administrative region (such as a state, province, or similar division) from which an entity originates or is associated by origin.
-
B.
regionFrom
chosen
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
C.
sourceRegion
Indicates the geographic or spatial region from which something originates or is derived.
-
D.
originSubregion
Indicates the specific subregional area from which an entity originates or is derived.
-
E.
calendarRegionOfOrigin
Indicates the geographic or cultural region from which a particular calendar system originates.
- 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_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 1, 2026, 1:59 a.m.