Triple
T36675633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blakeley |
E905534
|
entity |
| Predicate | hasOriginInToponym |
P97773
|
FINISHED |
| Object | places named Blakeley or similar in England |
—
|
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: places named Blakeley or similar in England | Statement: [Blakeley, hasOriginInToponym, places named Blakeley or similar in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginInToponym Context triple: [Blakeley, hasOriginInToponym, places named Blakeley or similar in England]
-
A.
hasOriginToponym
chosen
Indicates that something originates from, or is derived from, the place denoted by a specific toponym (geographical name).
-
B.
isToponymIn
Indicates that a place name (toponym) is located within or refers to a specific geographic area or region.
-
C.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
-
D.
hasTypeOfToponym
Indicates that one entity is classified as a specific type or category of toponym (place name) in relation to another entity.
-
E.
isToponymOf
Indicates that one entity is a place name (toponym) that refers to the location represented by the other entity.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69feff70fbec8190b1ff5f943f29613e |
completed | May 9, 2026, 9:33 a.m. |
| PD | Predicate disambiguation | batch_69fefbcd5b7881909cfe52b32f8a4301 |
completed | May 9, 2026, 9:18 a.m. |
Created at: May 3, 2026, 4:12 p.m.