Triple
T10663105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Embassy of Poland in Berlin |
E251276
|
entity |
| Predicate | hasMissionScope |
P13281
|
FINISHED |
| Object | political |
—
|
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: political | Statement: [Embassy of Poland in Berlin, hasMissionScope, political]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMissionScope Context triple: [Embassy of Poland in Berlin, hasMissionScope, political]
-
A.
hasMissionSystem
Indicates that an entity is equipped with or associated with a specific mission-related system or subsystem.
-
B.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
C.
missionScope
chosen
Indicates the defined range, objectives, and boundaries within which a mission or operation is intended to be carried out.
-
D.
hasMissionActivity
Indicates that an entity is associated with, performs, or is involved in a specific mission-related activity.
-
E.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
- 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_69d6aa5b0d2881909584b20efc5877f0 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6f31db6288190857533213fa9f20d |
completed | April 9, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:08 p.m.