Triple
T31030164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Albert (1916) |
E790699
|
entity |
| Predicate | BritishKilledFirstDay |
P17245
|
FINISHED |
| Object | about 19,000 |
—
|
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: about 19,000 | Statement: [Battle of Albert (1916), BritishKilledFirstDay, about 19,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BritishKilledFirstDay Context triple: [Battle of Albert (1916), BritishKilledFirstDay, about 19,000]
-
A.
casualtiesUKKilled
chosen
Indicates that the relationship specifies the number of people from the UK who were killed in the referenced event or incident.
-
B.
BritishCommanderKilledInAction
Indicates that a British military commander was killed while actively engaged in combat operations.
-
C.
militaryForceInvolved (British)
Indicates that the British military forces participated in or were involved in the referenced event or action.
-
D.
EnglandOversFaced
Indicates the total number of overs that England has faced while batting in a given cricket match or innings.
-
E.
BritishForceRole
Indicates that an entity serves in a specific role or capacity within a British military or armed forces context.
- 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 8:59 p.m.