Triple
T36697224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mach-1 |
E906124
|
entity |
| Predicate | previousAlignmentOfUser |
P174762
|
FINISHED |
| Object | supervillain |
—
|
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: supervillain | Statement: [Mach-1, previousAlignmentOfUser, supervillain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousAlignmentOfUser Context triple: [Mach-1, previousAlignmentOfUser, supervillain]
-
A.
previousAlignment
Indicates that one entity’s alignment or orientation occurred earlier in time than another’s.
-
B.
previousPlacement
Indicates that one entity occupied a position, role, or location before another specified placement or assignment.
-
C.
alignmentHistory
chosen
Indicates the historical record of how an entity’s alignment or stance has changed or been maintained over time in relation to another entity or standard.
-
D.
originallyAlignedWith
Indicates that an entity was initially in agreement, support, or association with another entity or group, regardless of any later changes in stance or affiliation.
-
E.
previousPositionWithTeam
Indicates that an entity previously held a position or role with a specified team before their current or later role.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: May 3, 2026, 4:12 p.m.