Triple
T33083103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asteroid M |
E846558
|
entity |
| Predicate | frequentlyOpposedBy |
P437
|
FINISHED |
| Object | X-Men |
—
|
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: X-Men | Statement: [Asteroid M, frequentlyOpposedBy, X-Men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frequentlyOpposedBy Context triple: [Asteroid M, frequentlyOpposedBy, X-Men]
-
A.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposesLabel
Indicates that one entity expresses disagreement with, resistance to, or active opposition against another entity or its position.
-
C.
opposedFocus
Indicates that one entity’s focus, attention, or emphasis is directed in opposition to, or in contrast with, the focus of another entity.
-
D.
historicallyOpposedBy
Indicates that one entity has been the target of opposition, resistance, or antagonism from another entity over a historical period.
-
E.
opposedByGroup
Indicates that an action, proposal, or entity is met with opposition or resistance from a particular group.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:26 a.m.