Triple
T31597389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4th Battalion, Royal 22e Régiment |
E806253
|
entity |
| Predicate | regimentalNickname |
P81025
|
FINISHED |
| Object | Van Doos |
—
|
NE NERFINISHED |
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: Van Doos | Statement: [4th Battalion, Royal 22e Régiment, regimentalNickname, Van Doos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalNickname Context triple: [4th Battalion, Royal 22e Régiment, regimentalNickname, Van Doos]
-
A.
hasRegimentalNickname
chosen
Indicates that a military regiment is associated with a specific informal or traditional nickname.
-
B.
regimentalMottoTranslation
Indicates the translated wording or meaning of a regiment’s official motto in another language.
-
C.
mottoOfRegiment
Indicates that a particular phrase or motto is officially associated with and represents a specific military regiment.
-
D.
regimentalTitle
Indicates the formal or official title assigned to a military regiment within an organizational or historical context.
-
E.
regimentalTitleAbbreviation
Indicates the abbreviated form of a regiment’s official title used to represent that regiment in shortened or symbolic notation.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10:31 p.m.