Triple
T17251685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thals |
E418767
|
entity |
| Predicate | opposedIdeologicallyTo |
P18907
|
FINISHED |
| Object | Dalek militarism |
—
|
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: Dalek militarism | Statement: [Thals, opposedIdeologicallyTo, Dalek militarism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedIdeologicallyTo Context triple: [Thals, opposedIdeologicallyTo, Dalek militarism]
-
A.
opposingIdeology
chosen
Indicates that two entities hold conflicting or mutually incompatible belief systems, doctrines, or ideological positions.
-
B.
opposingFactionIdeology
Indicates that two factions hold ideologies that are in direct conflict or fundamental opposition to each other.
-
C.
hasOpposedIdea
Indicates that one entity holds an idea that conflicts with, contradicts, or stands in opposition to the idea held by another entity.
-
D.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
E.
designedToOppose
Indicates that one entity is intentionally created or configured to counteract, resist, or work against another entity or process.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e694f788190a1c86e95264ed2fe |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.