Triple
T30397002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | siege of Kaiapoi Pā |
E773245
|
entity |
| Predicate | involvedIwi |
P1256
|
FINISHED |
| Object | Ngāi Tahu |
—
|
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: Ngāi Tahu | Statement: [siege of Kaiapoi Pā, involvedIwi, Ngāi Tahu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedIwi Context triple: [siege of Kaiapoi Pā, involvedIwi, Ngāi Tahu]
-
A.
involves
chosen
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
B.
involvedTown
Indicates that a town participates in, is associated with, or is affected by a particular event, activity, or relationship.
-
C.
unionInvolved
Indicates that a labor union is involved in, associated with, or plays a role in the specified action, event, or relationship between entities.
-
D.
rightInvolved
Indicates that an entity is involved in or associated with a legal or formal right held, exercised, or affected in a given context.
-
E.
involvedAction
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 29, 2026, 8:02 p.m.