Triple
T37962790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order Police |
E947049
|
entity |
| Predicate | successorInGermany |
P202846
|
FINISHED |
| Object | post-war German police forces |
—
|
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: post-war German police forces | Statement: [Order Police, successorInGermany, post-war German police forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorInGermany Context triple: [Order Police, successorInGermany, post-war German police forces]
-
A.
successorAsKingOfBavaria
Indicates that one person became the next king of Bavaria following another person’s reign.
-
B.
predecessorAsKingOfGermany
Indicates that one entity served as the immediately preceding king of Germany to the other entity.
-
C.
successorInAustria
Indicates that one entity directly follows another in a succession or sequence specifically within the context of Austria (e.g., in an office, role, or position).
-
D.
successorAsKingOfPrussia
Indicates that one person became the next king of Prussia following another person.
-
E.
succeededByAsKingOfGermany
Indicates that one person directly followed another as the reigning King of Germany.
- F. None of above. chosen
Provenance (4 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00c486d394819084fe93d5bb11ea1e |
completed | May 10, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_6a00c39d99d48190a94bfa057213499c |
completed | May 10, 2026, 5:42 p.m. |
| PDg | Predicate description generation | batch_6a00c48622b08190910d4dbc6db94c10 |
completed | May 10, 2026, 5:46 p.m. |
Created at: May 3, 2026, 4:20 p.m.