Triple
T23009992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaches—East York |
E572880
|
entity |
| Predicate | borderChangesOccurredIn |
P21193
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Beaches—East York, borderChangesOccurredIn, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderChangesOccurredIn Context triple: [Beaches—East York, borderChangesOccurredIn, 1987]
-
A.
borderChange
chosen
Indicates a change in the boundaries between geographic or political entities, such as when borders are redrawn, expanded, reduced, or otherwise altered over time.
-
B.
crossesBorderOf
Indicates that one entity passes from one side of the boundary of another entity (typically a region or area) to the other side, traversing its border.
-
C.
borderIsAffectedBy
Indicates that a border’s state, condition, or characteristics are influenced or changed by another factor or event.
-
D.
borderWithin
Indicates that one region’s border lies entirely inside the boundary of another region.
-
E.
borderIssue
Indicates a dispute, conflict, or problem related to the definition, control, or management of a boundary between two or more entities.
- 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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18359f5548190b15a139eb09e30a0 |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:51 p.m.