Triple
T25708729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkspolizei |
E644669
|
entity |
| Predicate | hadSpecialUnit |
P1198
|
FINISHED |
| Object | dog units |
—
|
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: dog units | Statement: [Volkspolizei, hadSpecialUnit, dog units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSpecialUnit Context triple: [Volkspolizei, hadSpecialUnit, dog units]
-
A.
hasSpecialUnit
chosen
Indicates that an entity possesses or is associated with a distinct, designated unit that has a special role, function, or status.
-
B.
hasSpecialMerit
Indicates that an entity possesses exceptional or noteworthy qualities that distinguish it from others in a positive way.
-
C.
isEliteUnit
Indicates that the unit belongs to a specially trained, highly capable subgroup distinguished from regular units.
-
D.
hadSpecialStatusIn
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
-
E.
hasSpecial
Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fc1385c4819082eff6432380dd2c |
completed | May 2, 2026, 1:28 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 9:08 p.m.