Triple
T4619833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Titans |
E100949
|
entity |
| Predicate | oftenOpposedBy |
P437
|
FINISHED |
| Object | younger gods |
—
|
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: younger gods | Statement: [Elder Titans, oftenOpposedBy, younger gods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenOpposedBy Context triple: [Elder Titans, oftenOpposedBy, younger gods]
-
A.
opposedBy
chosen
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposedConference
Indicates that one entity actively resists, counters, or works against another entity within the context of a conference or formal gathering.
-
C.
opposedByLeader
Indicates that an action, proposal, or position is actively resisted or rejected by a leader.
-
D.
historicallyOpposedBy
Indicates that one entity has been the target of opposition, resistance, or antagonism from another entity over a historical period.
-
E.
emergedInOppositionTo
Indicates that one entity came into existence or gained prominence specifically as a reaction or counter-movement against another entity.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59e3e6948190925e2cfad20dcc8c |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522fd5c48190ad2bffc0a5bc9061 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.