Triple
T35013001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonstar |
E1009980
|
entity |
| Predicate | hasPoliticalTensionBetween |
P53440
|
FINISHED |
| Object | Redguards |
—
|
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: Redguards | Statement: [Dragonstar, hasPoliticalTensionBetween, Redguards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliticalTensionBetween Context triple: [Dragonstar, hasPoliticalTensionBetween, Redguards]
-
A.
diplomaticTensionBetween
chosen
Indicates a strained or conflict-prone diplomatic relationship existing between two entities.
-
B.
doesNotHaveFormalPeaceTreatyWith
Indicates that no official, legally binding peace treaty exists between the two entities.
-
C.
politicalRelation
Indicates a relationship between entities that involves political alignment, influence, affiliation, conflict, or cooperation within a political context.
-
D.
hasDiplomaticStance
Indicates the type or nature of diplomatic relationship or attitude one entity holds toward another.
-
E.
hasMilitaryCooperationAt
Indicates that two or more entities engage in military cooperation at or in relation to a specific location or venue.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff3b32ee148190a3ba3b7600943fef |
completed | May 9, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69ff3a238af88190a2c2245e30299e48 |
completed | May 9, 2026, 1:44 p.m. |
Created at: May 3, 2026, 4:01 p.m.