Triple
T26942877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Walker |
E678564
|
entity |
| Predicate | mcuPlatform |
P161350
|
FINISHED |
| Object | Disney+ |
—
|
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: Disney+ | Statement: [John Walker, mcuPlatform, Disney+]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mcuPlatform Context triple: [John Walker, mcuPlatform, Disney+]
-
A.
MCUVariant
Indicates that one entity is a variant or alternate version of another within the Marvel Cinematic Universe continuity or multiverse.
-
B.
mcuVersion
Indicates the specific version or revision identifier of a microcontroller unit (MCU) associated with an entity.
-
C.
mcuProject
Indicates that an entity is a project associated with, based on, or belonging to the Marvel Cinematic Universe (MCU).
-
D.
hardwarePlatformFor
Indicates that one entity serves as the hardware platform on which another entity is designed to run or be deployed.
-
E.
hasMicrocontrollerCore
Indicates that one entity incorporates or contains a microcontroller core as part of its internal components or architecture.
- 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_69eeeb4d69588190a7c912164a1c37b3 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f620822d6081908e38814f5a1c0931 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
| PDg | Predicate description generation | batch_69f6125e54e0819088ee33a20efcc9e6 |
completed | May 2, 2026, 3:03 p.m. |
Created at: April 27, 2026, 6:19 a.m.