Triple
T38407254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merillon Avenue–Garden City Park |
E901365
|
entity |
| Predicate | refersToLocalities |
P188496
|
FINISHED |
| Object | Merillon Avenue |
—
|
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: Merillon Avenue | Statement: [Merillon Avenue–Garden City Park, refersToLocalities, Merillon Avenue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToLocalities Context triple: [Merillon Avenue–Garden City Park, refersToLocalities, Merillon Avenue]
-
A.
hasLocalities
Indicates that an entity is associated with, contains, or is linked to one or more specific geographic or administrative local areas.
-
B.
localityOf
chosen
Indicates that one entity is the specific place, area, or locality in which another entity is situated or occurs.
-
C.
coversLocality
Indicates that one entity spatially includes or encompasses the area or extent of a specified locality.
-
D.
hasTypeOfLocalities
Indicates that an entity is associated with, or classified by, specific types or categories of localities (e.g., urban, rural, suburban).
-
E.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
- 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_69f76e61e79c81908b787d83b46ab92b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 3, 2026, 4:31 p.m.