Triple
T7533152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11th Hussars |
E178076
|
entity |
| Predicate | equipmentRoleWWII |
P16542
|
FINISHED |
| Object | Armoured car regiment |
—
|
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: Armoured car regiment | Statement: [11th Hussars, equipmentRoleWWII, Armoured car regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equipmentRoleWWII Context triple: [11th Hussars, equipmentRoleWWII, Armoured car regiment]
-
A.
armamentWWII
Indicates that an entity served as a weapon, piece of equipment, or military hardware used during World War II.
-
B.
WWIIUse
Indicates that one entity made use of another entity during World War II, typically for military, strategic, or wartime-related purposes.
-
C.
worldWarIIRole
chosen
Indicates the specific role, position, or function an entity had in relation to World War II.
-
D.
historicalEquipment
Indicates that an entity is or involves equipment that was used in the past, typically in a historical or legacy context.
-
E.
roleInWorldWarI
Indicates the specific function, position, or involvement an entity had during World War I.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8493964819086aeddfa4872a70b |
completed | March 27, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d8eedc81908c1ae421e0e63798 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.