Triple
T37097545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auckland campus |
E918604
|
entity |
| Predicate | locatedInLargestCityOf |
P205725
|
FINISHED |
| Object | New Zealand |
E1850
|
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 | Statement: [Auckland campus, locatedInLargestCityOf, New Zealand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInLargestCityOf Context triple: [Auckland campus, locatedInLargestCityOf, New Zealand]
-
A.
locatedInCityWithSignificance
Indicates that an entity is located in a city that holds particular importance or notable significance (e.g., historical, cultural, political, or economic).
-
B.
usedInCapitalCityOf
Indicates that something is utilized or applied within the capital city of a specified region or country.
-
C.
locatedInCapital
Indicates that an entity is situated within the capital city of a specified region, country, or administrative area.
-
D.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
E.
locatedInCapitalCityPort
Indicates that something is situated within the port area of a country's capital city.
- F. None of above. chosen
Provenance (5 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3f69f769408190a51551d04c2e0d00 |
completed | June 27, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.