Triple
T16628886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France and Bavaria |
E404022
|
entity |
| Predicate | conflictResultAtBlenheim |
P21116
|
FINISHED |
| Object | decisive defeat |
—
|
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: decisive defeat | Statement: [France and Bavaria, conflictResultAtBlenheim, decisive defeat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflictResultAtBlenheim Context triple: [France and Bavaria, conflictResultAtBlenheim, decisive defeat]
-
A.
conflictResult
chosen
Indicates the outcome or consequence that arises from a particular conflict between entities.
-
B.
resultAtBattleOfTheFalklandIslands
Indicates the outcome or consequence that occurred specifically in the Battle of the Falkland Islands.
-
C.
facedConflictOver
Indicates that two or more entities experienced opposition, dispute, or tension concerning a particular issue, resource, or situation.
-
D.
engagementOutcomeAtBattleOfIquique
Indicates the result or outcome of a specific party’s engagement in the Battle of Iquique.
-
E.
conflictResolvedBy
Indicates that a conflict or dispute is settled or addressed through the actions, decisions, or intervention of a specified 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_69d883897eb481909eaaa088ba9918d9 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e378e399988190904e56eb3c490eed |
completed | April 18, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:17 a.m.