Triple
T5365495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Royal Hussars |
E103118
|
entity |
| Predicate | regimentalColonelTitle |
P63050
|
FINISHED |
| Object | Colonel of the 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: Colonel of the Regiment | Statement: [King’s Royal Hussars, regimentalColonelTitle, Colonel of the Regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalColonelTitle Context triple: [King’s Royal Hussars, regimentalColonelTitle, Colonel of the Regiment]
-
A.
colonelInChief
Indicates that one entity holds the ceremonial or honorary position of colonel-in-chief over a particular military unit or regiment.
-
B.
commanderTitle
Indicates the official rank or title held by the person who commands or leads a given entity.
-
C.
laterTitleOfCommander
Indicates that one title represents a later-held command position of the same commander who previously held another title.
-
D.
hasColonelInChief
Indicates that an organization or military unit has a designated ceremonial leader holding the title of Colonel-in-Chief.
-
E.
regimentalCategory
Indicates the classification or type of regiment to which a military unit or formation belongs.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865eb23481908d32fae4efd86efa |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd85731dcc8190b4c1fe155967ab81 |
completed | March 20, 2026, 5:35 p.m. |
Created at: March 20, 2026, 2:02 p.m.