Triple
T31102100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice League film series |
E792700
|
entity |
| Predicate | hasMainHeroTeam |
P108201
|
FINISHED |
| Object | Justice League |
—
|
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: Justice League | Statement: [Justice League film series, hasMainHeroTeam, Justice League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainHeroTeam Context triple: [Justice League film series, hasMainHeroTeam, Justice League]
-
A.
hasHeroTeam
chosen
Indicates a relationship where an entity is associated with or supported by a specific team of heroes.
-
B.
hasTeamSide
Indicates that an entity is associated with or belongs to a particular side or faction of a team within a competitive or collaborative context.
-
C.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
-
D.
hadChampionTeam
Indicates that an entity (such as a league, season, or competition) had a specific team recognized as its champion.
-
E.
hasHeroFaction
Indicates that an entity is associated with or belongs to a particular hero-aligned faction.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
Created at: April 29, 2026, 9:03 p.m.