Triple
T37717821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vision |
E939501
|
entity |
| Predicate | McuAffiliation |
P77873
|
FINISHED |
| Object | Avengers (MCU) |
—
|
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: Avengers (MCU) | Statement: [Vision, McuAffiliation, Avengers (MCU)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: McuAffiliation Context triple: [Vision, McuAffiliation, Avengers (MCU)]
-
A.
mcuAffiliation
chosen
Indicates the organizational or group alignment an entity has within the Marvel Cinematic Universe (e.g., which team, faction, or side they belong to).
-
B.
typicalCrewAffiliation
Indicates the usual or standard organizational group, team, or crew with which an entity is affiliated or associated.
-
C.
commanderAffiliation
Indicates that a commander is formally associated with, belongs to, or serves under a particular organization, group, or side.
-
D.
relationshipToMarvelUniverse
Indicates the nature or type of connection an entity has to the Marvel universe, such as affiliation, role, or relevance within that fictional setting.
-
E.
mainCharacterAffiliation
Indicates the group, organization, or side with which the main character is formally or primarily aligned.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.