Triple
T14542988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AMP Capital |
E341215
|
entity |
| Predicate | hasOfficeIn |
P1268
|
FINISHED |
| Object | Auckland |
E18491
|
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: Auckland | Statement: [AMP Capital, hasOfficeIn, Auckland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Auckland Context triple: [AMP Capital, hasOfficeIn, Auckland]
-
A.
Auckland
chosen
Auckland is a major New Zealand metropolis known for its harbors, multicultural population, and role as the country’s primary economic and transport hub.
-
B.
Wellington
Wellington is a regional town in New South Wales, Australia, known for its agricultural surroundings and location near the junction of the Macquarie and Bell rivers.
-
C.
Wellington
Wellington is a small town in northern Colorado, United States, located just north of Fort Collins and known as a growing residential community along the Interstate 25 corridor.
-
D.
Wellington
Wellington is a Chicago Transit Authority 'L' station on the Brown Line located in the Lakeview neighborhood of Chicago, Illinois.
-
E.
Wellington
Wellington is a small village in Lorain County, Ohio, known for its historic downtown and rural Midwestern character.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d822db9c8481908213ceb39585f792 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1be5a8081909bf727e28a5bba4a |
completed | April 14, 2026, 9:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd8ab5d50881908f53f8b7539c6fde |
completed | May 8, 2026, 7:03 a.m. |
Created at: April 10, 2026, 1:22 a.m.