Triple
T11669869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super-Soldier Formula |
E277348
|
entity |
| Predicate | MCUVariant |
P100692
|
FINISHED |
| Object | Super Soldier Serum |
—
|
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: Super Soldier Serum | Statement: [Super-Soldier Formula, MCUVariant, Super Soldier Serum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MCUVariant Context triple: [Super-Soldier Formula, MCUVariant, Super Soldier Serum]
-
A.
mcuVersion
Indicates the specific version or revision identifier of a microcontroller unit (MCU) associated with an entity.
-
B.
mcuProject
Indicates that an entity is a project associated with, based on, or belonging to the Marvel Cinematic Universe (MCU).
-
C.
hasMicrocontroller
Indicates that an entity contains, includes, or is equipped with a microcontroller as one of its components.
-
D.
hasMicrocontrollerCore
Indicates that one entity incorporates or contains a microcontroller core as part of its internal components or architecture.
-
E.
MCUFamily
Indicates a familial relationship between entities within the Marvel Cinematic Universe (MCU), such as by blood, marriage, or adoption.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a44264c08190ba1a4a5bcdc9367b |
completed | April 10, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69d88a77e6e88190b7519100bde76575 |
completed | April 10, 2026, 5:28 a.m. |
| PDg | Predicate description generation | batch_69d8938a1f8c81908ffb049fa5fee5a7 |
completed | April 10, 2026, 6:07 a.m. |
Created at: April 8, 2026, 9:39 p.m.