Triple
T29051219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marvel Comics adaptations |
E735264
|
entity |
| Predicate | notableTeamAdapted |
P203825
|
FINISHED |
| Object | The Avengers |
E59209
|
NE FINISHED |
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: The Avengers | Statement: [Marvel Comics adaptations, notableTeamAdapted, The Avengers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTeamAdapted Context triple: [Marvel Comics adaptations, notableTeamAdapted, The Avengers]
-
A.
notableTeamType
Indicates that an entity is notably associated with a team of a specified type (e.g., national team, club team, or other team category).
-
B.
notableTeams
Indicates that there is a noteworthy association between an entity and one or more teams with which it is significantly connected or recognized.
-
C.
notableChampionTeam
Indicates that a team is notably recognized as the champion associated with a particular competition, event, or context.
-
D.
notableIndependentTeam
Indicates that a team is independently organized or operated and is recognized as notable or significant in its context.
-
E.
notableTeamSeason
Indicates that a particular sports season is especially significant or noteworthy in the history of a given team.
- F. None of above. chosen
Provenance (5 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02145017b08190bd424cc647c08d3b |
completed | May 11, 2026, 5:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a262d421854819084ec60a79b97eac5 |
completed | June 8, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_6a021338e2b08190980c489ee44c18b3 |
completed | May 11, 2026, 5:34 p.m. |
| PDg | Predicate description generation | batch_6a02144f627c81909ead77e8e6b8f84f |
completed | May 11, 2026, 5:39 p.m. |
Created at: April 28, 2026, 10:08 a.m.