Triple
T29576978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I 9 |
E753469
|
entity |
| Predicate | regimentalDesignationFor |
P68774
|
FINISHED |
| Object | Skaraborg Regiment |
—
|
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: Skaraborg Regiment | Statement: [I 9, regimentalDesignationFor, Skaraborg Regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalDesignationFor Context triple: [I 9, regimentalDesignationFor, Skaraborg Regiment]
-
A.
regimentalCategory
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
B.
parentRegimentDesignation
Indicates that one military regiment is designated as the parent or higher-level regiment to which another regiment belongs or from which it is derived.
-
C.
regimentalNumber
Indicates the unique identifying number assigned to a member of a regiment, linking an individual to their specific regimental record.
-
D.
regimentalTitleAbbreviation
Indicates the abbreviated form of a regiment’s official title used to represent that regiment in shortened or symbolic notation.
-
E.
regimentalTitle
chosen
Indicates the formal or official title assigned to a military regiment within an organizational or historical 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d4b7f848190b6af93ae829a5caa |
completed | May 2, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:03 p.m.