Triple
T565864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czechoslovakia–West Germany border |
E13550
|
entity |
| Predicate | hadNoFreeMovement |
P11058
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Czechoslovakia–West Germany border, hadNoFreeMovement, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNoFreeMovement Context triple: [Czechoslovakia–West Germany border, hadNoFreeMovement, true]
-
A.
heldOn
Indicates that an event or activity takes place at a specific time, date, or occasion.
-
B.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
C.
didNotHold
Indicates that an expected event, condition, or relationship failed to occur or be valid.
-
D.
blockadedIn
Indicates that one entity is prevented or obstructed by another from entering, leaving, or accessing a particular place or resource.
-
E.
isDifficultToAccessBecauseOf
chosen
Indicates that something is hard to reach, obtain, or use due to a specified obstacle, condition, or circumstance.
- 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_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. |
Created at: March 1, 2026, 7:32 p.m.