Triple
T38593245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tactical Visor |
E932501
|
entity |
| Predicate | heroAffiliation |
P120153
|
FINISHED |
| Object | Overwatch (organization) |
—
|
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: Overwatch (organization) | Statement: [Tactical Visor, heroAffiliation, Overwatch (organization)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroAffiliation Context triple: [Tactical Visor, heroAffiliation, Overwatch (organization)]
-
A.
associatedWithSuperhero
Indicates that one entity has a notable connection, link, or involvement with a superhero entity.
-
B.
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.
-
C.
heroDepicted
Indicates that one entity is portrayed or represented as a hero in relation to another entity.
-
D.
characterAffiliationPortrayed
Indicates that a portrayal shows a character as being affiliated with a particular group, organization, or side.
-
E.
notableCharacterAffiliation
chosen
Indicates that a notable character is formally associated with, aligned to, or a member of a particular group, organization, or affiliation.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.