Triple
T29577004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P 4 |
E753470
|
entity |
| Predicate | regimentalName |
P63104
|
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: [P 4, regimentalName, Skaraborg Regiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimentalName Context triple: [P 4, regimentalName, Skaraborg Regiment]
-
A.
regimentalTitle
Indicates the formal or official title assigned to a military regiment within an organizational or historical context.
-
B.
regimentalCategory
Indicates the classification or type of regiment to which a military unit or formation belongs.
-
C.
militaryUnitName
chosen
Indicates the specific official name assigned to a military unit in the context of a broader relationship or record.
-
D.
hasRegimentalNickname
Indicates that a military regiment is associated with a specific informal or traditional nickname.
-
E.
regimentalFamily
Indicates a familial or close-kin relationship that exists within, or is defined by, a shared regimental or military unit affiliation.
- 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_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:03 p.m.