Triple
T17986976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Nancy |
E430260
|
entity |
| Predicate | outcomeForBurgundy |
P22603
|
FINISHED |
| Object | loss of ducal independence |
—
|
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: loss of ducal independence | Statement: [Battle of Nancy, outcomeForBurgundy, loss of ducal independence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outcomeForBurgundy Context triple: [Battle of Nancy, outcomeForBurgundy, loss of ducal independence]
-
A.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
B.
outcomeType
chosen
Indicates the specific category or nature of the result produced by an event, process, or action.
-
C.
importanceInBurgundy
Indicates the degree to which something holds significance, influence, or prominence within the context of Burgundy.
-
D.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
-
E.
subsequentOutcomeForWinner
Indicates that the predicate links a winner to an outcome or event that occurs to or for them after their initial victory.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29c6d0881909d450d2561d532a6 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.