Triple
T6343027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonel-in-Chief of the 4th Hussars |
E142677
|
entity |
| Predicate | natureOfRole |
P67836
|
FINISHED |
| Object | honorary |
—
|
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: honorary | Statement: [Colonel-in-Chief of the 4th Hussars, natureOfRole, honorary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureOfRole Context triple: [Colonel-in-Chief of the 4th Hussars, natureOfRole, honorary]
-
A.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
B.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
C.
natureOfOffice
chosen
Indicates the type or character of an office or position, specifying what kind of role or function it represents.
-
D.
role
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
E.
natureOfService
Indicates the specific type or category of service being provided or performed in a given 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_69c008d5ab108190b346c465696824a9 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06745b3d88190bcabc2bf5d75555d |
completed | March 22, 2026, 10:03 p.m. |
| PD | Predicate disambiguation | batch_69c060ea1a988190889e47b7e0c819b8 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:31 p.m.