Triple
T37471676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirnenn |
E931167
|
entity |
| Predicate | threatsOpposed |
P147428
|
FINISHED |
| Object | Drust forces in Ardenweald |
—
|
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: Drust forces in Ardenweald | Statement: [Tirnenn, threatsOpposed, Drust forces in Ardenweald]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatsOpposed Context triple: [Tirnenn, threatsOpposed, Drust forces in Ardenweald]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
threatsFaced
chosen
Indicates that an entity is exposed to or experiences specific dangers, risks, or harmful conditions.
-
C.
threatsDefendedAgainst
Indicates a relationship where one entity protects another from specific dangers, attacks, or harmful actions.
-
D.
opposedBecause
Indicates that one entity is opposed to another specifically due to a particular reason, cause, or justification.
-
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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.