Triple
T1941010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaiapoi |
E41552
|
entity |
| Predicate | wasEstablishedAs |
P5762
|
FINISHED |
| Object | European settlement in 1850s |
—
|
LITERAL 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: European settlement in 1850s | Statement: [Kaiapoi, wasEstablishedAs, European settlement in 1850s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEstablishedAs Context triple: [Kaiapoi, wasEstablishedAs, European settlement in 1850s]
-
A.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
B.
establishedAs
chosen
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
C.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
-
D.
establishedFrom
Indicates that something was created, founded, or formed starting from a specified source, origin, or prior entity.
-
E.
foundedAsResultOf
Indicates that one entity was established or created as a direct consequence or outcome of another event, action, or circumstance.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abaff25a588190bb4cbc8df9fc6d64 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.