Triple
T23470427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Checkpoint C |
E569210
|
entity |
| Predicate | demarcatedBorderBetween |
P119115
|
FINISHED |
| Object | Soviet sector of Berlin |
—
|
NE NERFINISHED |
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: Soviet sector of Berlin | Statement: [Allied Checkpoint C, demarcatedBorderBetween, Soviet sector of Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demarcatedBorderBetween Context triple: [Allied Checkpoint C, demarcatedBorderBetween, Soviet sector of Berlin]
-
A.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
B.
borderDefinedBetween
Indicates that a boundary line or border is formally established between two geographic or political entities.
-
C.
borderSectionOf
Indicates that one entity represents a specific segment or portion of the overall border of another entity.
-
D.
wasDemarcatedBetween
chosen
Indicates that a boundary or dividing line was formally established separating one entity from another.
-
E.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a6ff8dc0819086961b1f07030d9c |
completed | April 29, 2026, 6:36 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.