Triple
T31706294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moana universe |
E809188
|
entity |
| Predicate | primaryDeuteragonist |
P103401
|
FINISHED |
| Object | Maui |
E1129369
|
NE 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: Maui | Statement: [Moana universe, primaryDeuteragonist, Maui]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryDeuteragonist Context triple: [Moana universe, primaryDeuteragonist, Maui]
-
A.
secondaryProtagonistType
Indicates the role or category of a work’s secondary main character in relation to the primary protagonist.
-
B.
laterMainCharacterOf
Indicates that one entity becomes the main character of a work at a later point in time, succeeding another main character.
-
C.
hasSecondaryProtagonist
chosen
Indicates that an entity (such as a work of fiction) features another character who serves as a secondary or supporting main protagonist alongside the primary one.
-
D.
supportingCharacter
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
E.
secondaryProtagonistCelebrated
Indicates that a secondary protagonist is being honored, praised, or widely recognized for their actions or role.
- F. None of above.
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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2d9d430670819090389fc42c354956 |
completed | June 13, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 11:14 p.m.