Triple
T26770564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Berlin Police |
E675064
|
entity |
| Predicate | hadPrimaryMission |
P105991
|
FINISHED |
| Object | protection of West Berlin citizens |
—
|
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: protection of West Berlin citizens | Statement: [West Berlin Police, hadPrimaryMission, protection of West Berlin citizens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPrimaryMission Context triple: [West Berlin Police, hadPrimaryMission, protection of West Berlin citizens]
-
A.
hadMission
chosen
Indicates that an entity (such as a person, organization, or vehicle) was assigned or carried out a specific mission or operation.
-
B.
laterPrimaryMission
Indicates that one mission occurs after another mission in the sequence of primary missions.
-
C.
hasMissionTo
Indicates that an entity is assigned or dedicated to carrying out a specific mission, task, or purpose related to another entity or objective.
-
D.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
-
E.
performedMission
Indicates that an agent has carried out or completed a specific mission or task.
- 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_69eecda85298819097ee1c38a3d772e7 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6192c45fc819094e7dd70fd9cc333 |
completed | May 2, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 4:02 a.m.