Triple
T6961566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Light Brigade |
E161379
|
entity |
| Predicate | resultOfCharge |
P73802
|
FINISHED |
| Object | tactical failure |
—
|
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: tactical failure | Statement: [British Light Brigade, resultOfCharge, tactical failure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfCharge Context triple: [British Light Brigade, resultOfCharge, tactical failure]
-
A.
chargeDetail
Indicates a detailed specification of a financial charge, including its components, conditions, or breakdown within a transaction or billing context.
-
B.
repaymentOutcome
Indicates the result or status of a repayment action, such as whether it was completed, failed, or partially fulfilled.
-
C.
chargesVia
Indicates that one entity charges or powers another entity using a specified medium, method, or interface.
-
D.
paymentPlaced
Indicates that a payment has been initiated or submitted for processing in relation to a specific transaction or obligation.
-
E.
commissionOutcome
Indicates the result or consequence produced by a commission, such as whether it was successful, failed, or led to a particular decision or action.
- 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_69c68853cff881908439d488924a8283 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6daf07e3481909aa79b8e0f1b1be7 |
completed | March 27, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c0b0a08190b262dfc94992994d |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d9bb57e88190a3a7cec34e3b617f |
completed | March 27, 2026, 7:25 p.m. |
Created at: March 27, 2026, 2:30 p.m.