Triple
T15846065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tama-nui-te-rā |
E384215
|
entity |
| Predicate | resultOfConflictWithMāui |
P120104
|
FINISHED |
| Object | slowed daily journey |
—
|
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: slowed daily journey | Statement: [Tama-nui-te-rā, resultOfConflictWithMāui, slowed daily journey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfConflictWithMāui Context triple: [Tama-nui-te-rā, resultOfConflictWithMāui, slowed daily journey]
-
A.
hasMoaiWithPukao
Indicates that something includes or features a moai statue that is specifically topped with a pukao (a stone hat or topknot).
-
B.
sideTakenInTitanomachy
Indicates which faction or side an entity aligned with or supported during the Titanomachy conflict.
-
C.
combatOutcomeWithTheseus
Indicates the result or consequence of a combat encounter involving Theseus and another entity.
-
D.
methodOfRevenge
Indicates a relationship where a specific action or strategy is used as the means by which revenge is carried out.
-
E.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
- F. None of above. chosen
Provenance (4 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e14ca636048190bc89cd8b4efa89e9 |
completed | April 16, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69e005434ed88190baf11c169da3cf29 |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007869ae481909473ee220a7ccdb5 |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:50 a.m.