Triple
T36303920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawkeye (2012) |
E893893
|
entity |
| Predicate | teamAffiliationDepicted |
P131760
|
FINISHED |
| Object | Avengers |
—
|
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 | Statement: [Hawkeye (2012), teamAffiliationDepicted, Avengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamAffiliationDepicted Context triple: [Hawkeye (2012), teamAffiliationDepicted, Avengers]
-
A.
teamAffiliations
Indicates that one entity is or has been a member of, associated with, or officially aligned to a particular team.
-
B.
playerAffiliation
Indicates the organization, team, or group with which a player is formally associated or aligned.
-
C.
team2Affiliation
Indicates that an entity is affiliated with, belongs to, or is associated with a second team in a given context.
-
D.
teamAffiliationInStory
chosen
Indicates that, within the context of a particular story, one entity is affiliated with or belongs to a specific team.
-
E.
teamAffiliationStructure
Indicates the organizational relationship that defines how a team is structured, including its internal roles, hierarchy, and affiliations.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.