Triple
T20048821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Highland Fusiliers |
E499135
|
entity |
| Predicate | usesFusilierTraditions |
P51653
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Royal Highland Fusiliers, usesFusilierTraditions, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFusilierTraditions Context triple: [Royal Highland Fusiliers, usesFusilierTraditions, yes]
-
A.
FrenchArmourUsed
Indicates that French-made armor was employed or utilized in a particular context or event.
-
B.
militaryTradition
Indicates a relationship where a group, place, or institution is associated with a specific historical or cultural practice of military service, customs, or heritage.
-
C.
regimentalTradition
chosen
Indicates a relationship where a specific custom, practice, or set of values is traditionally associated with and maintained by a particular military regiment.
-
D.
usesFirearmsUnit
Indicates that one entity employs or operates firearms as part of a specific unit or organizational grouping.
-
E.
FrenchImperialGunsLost
Indicates that French imperial forces lost their artillery or guns in a particular event or 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632c085081908710cbc939ac9971 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.