Triple
T16111012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hendon North |
E390874
|
entity |
| Predicate | boundaryChangesOccurred |
P21193
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hendon North, boundaryChangesOccurred, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundaryChangesOccurred Context triple: [Hendon North, boundaryChangesOccurred, yes]
-
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.
boundaryReviewEvent
Indicates an event in which the boundaries or limits of something are formally examined, evaluated, or adjusted.
-
C.
changesWith
Indicates that one entity varies or is modified in response to changes in another entity.
-
D.
segmentChange
Indicates a change or transition from one defined segment or phase to another within a sequence or process.
-
E.
surfaceChange
Indicates a change in the physical surface characteristics or condition of an entity over time or due to some event or interaction.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016718ec8190a6c8284c7f612ea8 |
completed | April 17, 2026, 9:46 a.m. |
| PD | Predicate disambiguation | batch_69e1828518c48190a8ef3aaa46a1f639 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5 a.m.