Triple
T33238702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Tribes of New Zealand |
E850904
|
entity |
| Predicate | dateFormedApprox |
P166826
|
FINISHED |
| Object | early 1830s |
—
|
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: early 1830s | Statement: [United Tribes of New Zealand, dateFormedApprox, early 1830s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateFormedApprox Context triple: [United Tribes of New Zealand, dateFormedApprox, early 1830s]
-
A.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
B.
dateFormedFrom
Indicates that one date value is derived or constructed from another date or date-related source.
-
C.
unificationApproximateDate
chosen
Indicates that two entities became unified or merged around an estimated or approximate date rather than a precisely known time.
-
D.
approximateDepictionDate
Indicates the estimated or inferred date when a depiction was created, rather than a precise, confirmed date.
-
E.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
- 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_69f349613f988190a1eb75467d167122 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:31 a.m.