Triple
T30651523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blaze and the Monster Machines |
E780270
|
entity |
| Predicate | AJRole |
P90497
|
FINISHED |
| Object | driver of Blaze |
—
|
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: driver of Blaze | Statement: [Blaze and the Monster Machines, AJRole, driver of Blaze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AJRole Context triple: [Blaze and the Monster Machines, AJRole, driver of Blaze]
-
A.
authorityRole
Indicates that one entity holds an official position or role that grants it authority or control over another entity or within a specific context.
-
B.
eraRole
Indicates the specific role, function, or capacity an entity has within a particular historical or temporal era.
-
C.
antRole
chosen
Indicates that one entity has a specific role, function, or responsibility in relation to another entity.
-
D.
CDCRole
Indicates that one entity holds a specific role or function within a clinical data collection (CDC) context relative to another entity.
-
E.
unitRole
Indicates the functional role or purpose that a unit serves within a larger system 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a98249081909b4be467f5a37110 |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:30 p.m.