Triple
T9513948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepper Pike |
E229473
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Mayfield Heights |
E238531
|
NE 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: Mayfield Heights | Statement: [Pepper Pike, adjacentTo, Mayfield Heights]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mayfield Heights Context triple: [Pepper Pike, adjacentTo, Mayfield Heights]
-
A.
Mayfield Heights
chosen
Mayfield Heights is a suburban city in northeastern Ohio, located east of Cleveland and known for its residential neighborhoods and commercial corridors.
-
B.
Cleveland Heights
Cleveland Heights is an inner-ring suburban city of Cleveland in northeastern Ohio, known for its historic neighborhoods, cultural diversity, and vibrant arts and dining scenes.
-
C.
Middleburg Heights
Middleburg Heights is a suburban city in northeastern Ohio, located within the Greater Cleveland metropolitan area.
-
D.
Cuyahoga Heights
Cuyahoga Heights is a small village located in Cuyahoga County, Ohio, known for its industrial base and proximity to Cleveland.
-
E.
Garfield Heights
Garfield Heights is a suburban city located southeast of downtown Cleveland in northeastern Ohio.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca84777560819084cddd999badc1aa |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd986bfcac8190aa97f8975cb17f6c |
completed | April 1, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2696450e4819086d5aac368127e5f |
completed | April 5, 2026, 1:53 p.m. |
Created at: March 30, 2026, 7:58 p.m.