Triple
T565862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czechoslovakia–West Germany border |
E13550
|
entity |
| Predicate | controlledByOnWest |
P16435
|
FINISHED |
| Object | West German border guards |
—
|
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: West German border guards | Statement: [Czechoslovakia–West Germany border, controlledByOnWest, West German border guards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledByOnWest Context triple: [Czechoslovakia–West Germany border, controlledByOnWest, West German border guards]
-
A.
locatedWestOf
Indicates that one entity is positioned geographically to the west of another entity.
-
B.
teamCityControlled
Indicates that a particular team has control or authority over a given city.
-
C.
liesNorthwestOf
Indicates that one entity is located to the northwest of another entity, combining both a more northern and more western position relative to it.
-
D.
controlled
Indicates that one entity has power, authority, or influence to direct, regulate, or determine the behavior, actions, or state of another entity.
-
E.
locatedNorthwestOf
Indicates that one entity is positioned to the northwest of another entity in space or geography.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a74793481908fee3baff0b1d348 |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c183b081909304944aa3d0fe8f |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985952a481908b918350ececf484 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.