Triple
T27872113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D’Qar |
E704816
|
entity |
| Predicate | factionOpposed |
P130604
|
FINISHED |
| Object | First Order |
—
|
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: First Order | Statement: [D’Qar, factionOpposed, First Order]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionOpposed Context triple: [D’Qar, factionOpposed, First Order]
-
A.
opposingPoliticalFaction
chosen
Indicates that two entities belong to political groups or factions that are in conflict or opposition to each other.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
opposition
Indicates a relationship in which one entity actively resists, disagrees with, or is positioned against another entity, idea, or action.
-
D.
opposedByGroup
Indicates that an action, proposal, or entity is met with opposition or resistance from a particular group.
-
E.
opposesDivision
Indicates a relationship where one entity actively resists, rejects, or works against the separation or splitting of another entity into parts or groups.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6397cafe081909ab66f1072c4888d |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:25 p.m.