Triple
T37718917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omega Flight |
E939529
|
entity |
| Predicate | hasAlternateRoster |
P165024
|
FINISHED |
| Object | villainous version |
—
|
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: villainous version | Statement: [Omega Flight, hasAlternateRoster, villainous version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateRoster Context triple: [Omega Flight, hasAlternateRoster, villainous version]
-
A.
hasRostersFor
Indicates that an entity maintains or provides one or more rosters associated with another entity, context, or time period.
-
B.
hasExpandedRoster
Indicates that an entity’s roster, lineup, or membership has increased in size compared to a previous state.
-
C.
hasAlternativeProfile
chosen
Indicates that an entity is associated with another profile that serves as an alternative or secondary representation of it.
-
D.
hasRosterStatus
Indicates the current membership or availability status of an entity within a defined roster or lineup.
-
E.
hasAlternateHero
Indicates that an entity is associated with a different or substitute hero that can take its place or serve as an alternative.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:18 p.m.