Triple
T565847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czechoslovakia–West Germany border |
E13550
|
entity |
| Predicate | demarcatedBy |
P14046
|
FINISHED |
| Object | border markers |
—
|
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: border markers | Statement: [Czechoslovakia–West Germany border, demarcatedBy, border markers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demarcatedBy Context triple: [Czechoslovakia–West Germany border, demarcatedBy, border markers]
-
A.
demarcationType
Indicates the specific way in which a boundary or separation between entities is defined, marked, or categorized.
-
B.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
-
C.
borderDefinedBy
chosen
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
D.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
E.
separatedInto
Indicates that something has been divided or split into distinct parts, groups, or components.
- 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.