Triple
T31543449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Vincy |
E804808
|
entity |
| Predicate | losingSide |
P49115
|
FINISHED |
| Object | Neustrian royal faction |
—
|
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: Neustrian royal faction | Statement: [Battle of Vincy, losingSide, Neustrian royal faction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: losingSide Context triple: [Battle of Vincy, losingSide, Neustrian royal faction]
-
A.
losingState
Indicates that a particular game or competitive situation is in a condition where the player or side in question is currently losing or destined to lose under optimal play.
-
B.
loserParty
Indicates that a particular political party was the one that lost in a given election or contest.
-
C.
sideLost
chosen
Indicates that a particular side, party, or team was defeated or failed to win in a contest, conflict, or competition.
-
D.
loserStatus
Indicates that an entity has been judged or designated as the loser in a particular comparison, contest, or evaluative context.
-
E.
loserScore
Indicates the number of points or score achieved by the losing participant in a competitive event or comparison.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8055f8081908f635fe04654b5fe |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:07 p.m.