Triple
T4124906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Air Service Regiment |
E92700
|
entity |
| Predicate | upgradedToRegiment |
P54423
|
FINISHED |
| Object | 1964 |
—
|
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: 1964 | Statement: [Special Air Service Regiment, upgradedToRegiment, 1964]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradedToRegiment Context triple: [Special Air Service Regiment, upgradedToRegiment, 1964]
-
A.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
-
B.
promotedToAdmiral
Indicates that an entity has been elevated in rank or position to the status of admiral.
-
C.
promotedToMajorGeneralOfVolunteers
Indicates that a person was elevated in rank to serve as a major general within a volunteer military force.
-
D.
elevatedToMilitaryOrdinariate
Indicates that an entity has been raised in status or jurisdiction to become a military ordinariate (a special ecclesiastical jurisdiction for armed forces).
-
E.
militaryRankProgression
Indicates the sequence or advancement of an individual’s positions within a structured military rank hierarchy.
- F. None of above. chosen
Provenance (4 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0245adbc81908b89a40850047975 |
completed | March 9, 2026, 5:24 p.m. |
Created at: March 9, 2026, 3:41 p.m.