Triple
T35595699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Essex Regiment |
E1028623
|
entity |
| Predicate | notableWorldWarIUnit |
—
|
GENERATED |
| Object | 1st Battalion, Essex Regiment |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorldWarIUnit Context triple: [Essex Regiment, notableWorldWarIUnit, 1st Battalion, Essex Regiment]
-
A.
notableMilitaryUnit
chosen
Indicates that an entity is a military unit that holds particular significance, prominence, or recognition in some context.
-
B.
crewComplementWWI
Indicates the number and composition of crew members assigned to an entity (such as a vessel or unit) during World War I.
-
C.
militaryUnitName
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
-
D.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
-
E.
serviceBranchDuringWorldWarI
Indicates that an entity served in a specified military branch during World War I.
- F. None of above.
Provenance (1 batch)
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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.