Triple
T9447844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 48th Highlanders of Canada |
E227809
|
entity |
| Predicate | languageOfParadeCommands |
P6537
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [48th Highlanders of Canada, languageOfParadeCommands, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfParadeCommands Context triple: [48th Highlanders of Canada, languageOfParadeCommands, English]
-
A.
languageOfCommand
chosen
Indicates that a specified language is the one in which a given command is expressed or issued.
-
B.
languageOfYells
Indicates a relationship where a particular language is used as the medium or form of someone’s yelling or shouted expressions.
-
C.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
D.
languageOfOperation
Indicates the language in which an entity (such as a system, service, or process) primarily operates or functions.
-
E.
EnglishCommander
Indicates that one entity serves as a military commander or leader for English forces in relation to another entity.
- 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_69ca8439f8bc8190997f2ef40c9f0bc2 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f62dfa48190bf318777d97f0f2a |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:51 p.m.