Triple
T33668460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queenstown Planning Area |
E862554
|
entity |
| Predicate | hasPlanningCode |
P190702
|
FINISHED |
| Object | Queenstown |
E1734606
|
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: Queenstown | Statement: [Queenstown Planning Area, hasPlanningCode, Queenstown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlanningCode Context triple: [Queenstown Planning Area, hasPlanningCode, Queenstown]
-
A.
planningCode
chosen
Indicates that an entity is associated with a specific planning classification or code used to govern or describe how it should be planned or managed.
-
B.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
C.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
D.
hasPlanningCharacteristic
Indicates that an entity possesses a specific feature, quality, or attribute related to planning activities or processes.
-
E.
hasPlanningFunction
Indicates that an entity is responsible for or involved in planning, organizing, or determining future actions or strategies.
- F. None of above.
Provenance (4 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a363c8e29b08190852a4102d3d9528e |
completed | June 20, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: May 1, 2026, 1:42 a.m.