Triple
T11122957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolts* (upcoming film) |
E263062
|
entity |
| Predicate | featuresTeamType |
P2705
|
FINISHED |
| Object | antiheroes |
—
|
LITERAL 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: antiheroes | Statement: [Thunderbolts* (upcoming film), featuresTeamType, antiheroes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTeamType Context triple: [Thunderbolts* (upcoming film), featuresTeamType, antiheroes]
-
A.
typeOfTeams
chosen
Indicates the categories or kinds of teams to which an entity or group of entities belongs.
-
B.
featuredTeam
Indicates that a particular team is highlighted or given special prominence in a given context or presentation.
-
C.
fieldsTeam
Indicates that an entity is a member of, or associated as part of, a particular team.
-
D.
teamNameType
Indicates the type or category associated with a team's name (e.g., formal name, short name, nickname).
-
E.
featuresOpponentType
Indicates that an entity involves, includes, or is associated with an opponent of a specified type within a competitive or adversarial context.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7e82e933481908550499cf9dd6531 |
completed | April 9, 2026, 5:55 p.m. |
| PD | Predicate disambiguation | batch_69d7441efe948190ae4ab020121e169d |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:28 p.m.