Triple
T20048828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Highland Fusiliers |
E499135
|
entity |
| Predicate | typeOfFusiliersRegiment |
P56207
|
FINISHED |
| Object | Scottish fusiliers |
—
|
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: Scottish fusiliers | Statement: [Royal Highland Fusiliers, typeOfFusiliersRegiment, Scottish fusiliers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFusiliersRegiment Context triple: [Royal Highland Fusiliers, typeOfFusiliersRegiment, Scottish fusiliers]
-
A.
regimentalCategory
chosen
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
B.
guardRegiment
Indicates that one entity serves as a protective or security regiment for another entity.
-
C.
regimentalFamily
Indicates a familial or close-kin relationship that exists within, or is defined by, a shared regimental or military unit affiliation.
-
D.
typeOfCadetForce
Indicates the specific category or kind of cadet force to which an entity belongs.
-
E.
notableMilitaryUnit
Indicates that an entity is a military unit that holds particular significance, prominence, or recognition in some 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.