Triple
T32313601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tākitimu |
E825567
|
entity |
| Predicate | hasCaptainInTradition |
P134443
|
FINISHED |
| Object | Tamatea-arikinui |
—
|
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: Tamatea-arikinui | Statement: [Tākitimu, hasCaptainInTradition, Tamatea-arikinui]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaptainInTradition Context triple: [Tākitimu, hasCaptainInTradition, Tamatea-arikinui]
-
A.
captaincyTradition
chosen
Indicates a customary or historically established practice regarding who holds or assumes the role of captain in a given context.
-
B.
hasNotableCaptain
Indicates that an entity has a specific captain who is recognized as notable or distinguished in some way.
-
C.
hasCaptainsFormatParticipation
Indicates that an entity participates in a competition, event, or context specifically in the role or format of a captain.
-
D.
captainServedUnder
Indicates that one captain performed their service or held their position under the authority or command of another person.
-
E.
servedAsCaptainFrom
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fed357b2b4819084c709056a54461f |
completed | May 9, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_69fed103d9cc81909b11619745110c61 |
completed | May 9, 2026, 6:15 a.m. |
Created at: May 1, 2026, 12:46 a.m.