Triple
T35470554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion of Doom |
E1025194
|
entity |
| Predicate | hasOpposingTeam |
P172640
|
FINISHED |
| Object | Justice League of America |
—
|
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 of America | Statement: [Legion of Doom, hasOpposingTeam, Justice League of America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOpposingTeam Context triple: [Legion of Doom, hasOpposingTeam, Justice League of America]
-
A.
hasOpposingTeamsLedBy
Indicates a relationship where a competitive event or context features two opposing teams, each directed or managed by a specific leader.
-
B.
hasOpposingSide
Indicates that one entity possesses or is associated with another entity that lies on the opposite or facing side relative to a reference orientation or boundary.
-
C.
hasOpposingAlliance
Indicates that two entities belong to alliances or factions that are in direct opposition or conflict with each other.
-
D.
teamOpposed
chosen
Indicates that one team is in opposition or conflict with another team, such as being rivals or competing against each other.
-
E.
opponentTeamsAffected
Indicates that the specified action, condition, or effect applies to the teams designated as opponents.
- 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_69f76dfa20d0819089585dc2cf653aea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:04 p.m.