Triple
T31983486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Action at Nicholson’s Nek |
E816650
|
entity |
| Predicate | operationOutcome |
P92530
|
FINISHED |
| Object | failed British night operation |
—
|
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: failed British night operation | Statement: [Action at Nicholson’s Nek, operationOutcome, failed British night operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operationOutcome Context triple: [Action at Nicholson’s Nek, operationOutcome, failed British night operation]
-
A.
administrativeOutcome
Indicates the result or consequence of an administrative process, decision, or action taken by an authority.
-
B.
serviceOutcome
Indicates the result, consequence, or effect produced by performing a particular service.
-
C.
outcomeSummary
chosen
Indicates a concise description or overview of the result or consequences of an action, event, or process.
-
D.
reportsOutcomeOf
Indicates that one entity communicates or provides the result, consequence, or final status of another entity’s process, event, or action.
-
E.
bodyOutcome
Indicates the resulting physical state or condition that occurs to a body as a consequence of an action or event.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
Created at: May 1, 2026, 12:12 a.m.