Triple
T18812581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te Kaunihera o Tāmaki Makaurau |
E460051
|
entity |
| Predicate | cameIntoExistenceOn |
P29675
|
FINISHED |
| Object | 2010-11-01 |
—
|
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: 2010-11-01 | Statement: [Te Kaunihera o Tāmaki Makaurau, cameIntoExistenceOn, 2010-11-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoExistenceOn Context triple: [Te Kaunihera o Tāmaki Makaurau, cameIntoExistenceOn, 2010-11-01]
-
A.
createdIn
Indicates that one entity was brought into existence, produced, or originated within the context, location, or time frame specified by another entity.
-
B.
createdTo
Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of another entity.
-
C.
existsSince
chosen
Indicates that an entity has been in existence or valid from a specified point in time onward.
-
D.
wasBornInto
Indicates that an entity entered existence as a member of a particular family, social group, or circumstance at birth.
-
E.
firstAppearsOnEarth
Indicates that the referenced entity makes its earliest known appearance or occurrence on Earth at the specified time or context.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3dcc7d88190801d9c9202e0e411 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.