Triple
T36554948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuiviénen |
E901676
|
entity |
| Predicate | resultOfSummons |
P194829
|
FINISHED |
| Object | Great Journey of the Eldar |
—
|
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: Great Journey of the Eldar | Statement: [Cuiviénen, resultOfSummons, Great Journey of the Eldar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfSummons Context triple: [Cuiviénen, resultOfSummons, Great Journey of the Eldar]
-
A.
summonsForOpponent
Indicates that one entity initiates or performs a summoning action on behalf of, or targeting, an opposing entity.
-
B.
legalOutcome
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
C.
judgmentResult
Indicates the outcome or decision produced by a judgment, such as a court ruling, evaluation, or formal assessment, regarding the entities involved.
-
D.
resultOfAccusation
Indicates that one entity is the outcome, consequence, or product of an accusation made by another entity.
-
E.
courtHeld
Indicates that a court has formally decided, ruled, or determined a particular legal issue or question.
- F. None of above. chosen
Provenance (4 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
| PDg | Predicate description generation | batch_69fd884b9d908190833de9500ff6d62a |
completed | May 8, 2026, 6:52 a.m. |
Created at: May 3, 2026, 4:11 p.m.