Triple
T32606721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvel Team-Up |
E833539
|
entity |
| Predicate | guestStarsCharacter |
P12208
|
FINISHED |
| Object | Human Torch |
—
|
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: Human Torch | Statement: [Marvel Team-Up, guestStarsCharacter, Human Torch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guestStarsCharacter Context triple: [Marvel Team-Up, guestStarsCharacter, Human Torch]
-
A.
guestStar
Indicates that one entity appears in a limited, special, or featured role within another entity’s production, event, or context, without being a regular or primary participant.
-
B.
cameoCharacter
Indicates that one entity appears briefly or in a minor, special-guest role within the context or work associated with another entity.
-
C.
characterIn
chosen
Indicates that an entity appears as a character within a specified work, story, or narrative.
-
D.
hasFictionalCoStar
Indicates that one entity appears as a co-star alongside another entity within a fictional work or narrative.
-
E.
characterPerformer
Indicates that a performer portrays or voices a particular character in a work.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c6c719488190b91df99a88a5119b |
completed | May 3, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:05 a.m.