Triple
T37467050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titans (Crash: Mind over Mutant) |
E931057
|
entity |
| Predicate | controlledUsing |
P49579
|
FINISHED |
| Object | Aku Aku mask |
—
|
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: Aku Aku mask | Statement: [Titans (Crash: Mind over Mutant), controlledUsing, Aku Aku mask]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledUsing Context triple: [Titans (Crash: Mind over Mutant), controlledUsing, Aku Aku mask]
-
A.
usedToControl
chosen
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
B.
usedControl
Indicates that one entity exercised or applied a control mechanism or method over another entity or process.
-
C.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
D.
controlledIn
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
-
E.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 3, 2026, 4:17 p.m.