Triple
T27354326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mons 1914 |
E685642
|
entity |
| Predicate | primaryBritishForce |
P77746
|
FINISHED |
| Object | I Corps (BEF) |
—
|
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: I Corps (BEF) | Statement: [Mons 1914, primaryBritishForce, I Corps (BEF)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryBritishForce Context triple: [Mons 1914, primaryBritishForce, I Corps (BEF)]
-
A.
BritishForcesType
Indicates that an entity is classified as a type or category within the British armed forces.
-
B.
strengthBritishForces
Indicates the numerical size or combat capacity of British military forces in a given context or operation.
-
C.
militaryForceInvolved (British)
chosen
Indicates that the British military forces participated in or were involved in the referenced event or action.
-
D.
BritishForceRole
Indicates that an entity serves in a specific role or capacity within a British military or armed forces context.
-
E.
commandingOfficerBritishSide
Indicates that one entity serves as the commanding officer of another entity on the British side in a military 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: April 27, 2026, 11:50 a.m.