Triple
T29205877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Stone |
E740409
|
entity |
| Predicate | guardedByInMCU |
P96653
|
FINISHED |
| Object | Red Skull |
—
|
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: Red Skull | Statement: [Soul Stone, guardedByInMCU, Red Skull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedByInMCU Context triple: [Soul Stone, guardedByInMCU, Red Skull]
-
A.
obtainedByInMCU
Indicates that something is acquired or achieved by a character or entity within the Marvel Cinematic Universe (MCU).
-
B.
MCUGuardian
chosen
Indicates a guardian or protector relationship, where one entity is responsible for safeguarding or overseeing another within a specific context or system.
-
C.
roleInMCU
Indicates that one entity portrays or has a specific character role within the Marvel Cinematic Universe in relation to the other entity.
-
D.
guardedAs
Indicates that one entity is protected, watched over, or kept secure in the role or capacity specified by another entity.
-
E.
mcuPhase
Indicates the phase or installment of the Marvel Cinematic Universe in which an entity (such as a film, show, or event) belongs.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 12:09 p.m.