Triple
T10087385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 96th Regiment of Foot |
E215254
|
entity |
| Predicate | militaryUnitNumber |
P18684
|
FINISHED |
| Object | 96 |
—
|
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: 96 | Statement: [96th Regiment of Foot, militaryUnitNumber, 96]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryUnitNumber Context triple: [96th Regiment of Foot, militaryUnitNumber, 96]
-
A.
regimentalNumber
chosen
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
-
B.
militaryUnitName
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
-
C.
militaryUnitOf
Indicates that one entity is a military unit that belongs to, is part of, or is under the command or organizational structure of another entity.
-
D.
hasBattalionNumber
Indicates that an entity (such as a military unit) is associated with a specific battalion number identifier.
-
E.
armedForcesBranchNumber
Indicates the specific numerical designation or identifier assigned to a branch of the armed forces within a military organization.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04875748190a81d1e9ad68dda96 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:01 p.m.