Triple
T22510389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Londres 38 |
E556502
|
entity |
| Predicate | locatedOnStreet |
P959
|
FINISHED |
| Object | Calle Londres |
—
|
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: Calle Londres | Statement: [Londres 38, locatedOnStreet, Calle Londres]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Calle Londres Context triple: [Londres 38, locatedOnStreet, Calle Londres]
-
A.
Calle Londres
chosen
Calle Londres is a prominent street in Mexico City's Zona Rosa district, known for its shops, restaurants, nightlife, and vibrant urban atmosphere.
-
B.
London Road
London Road is a major thoroughfare in Edinburgh, Scotland, forming part of the main eastern approach to the city centre.
-
C.
London Road
London Road is a main shopping street in Enfield Town, featuring a variety of retail stores and local businesses.
-
D.
London Road
London Road is a common street name in Guildford, Surrey, England, typically referring to a main thoroughfare leading toward or historically associated with the route to London.
-
E.
London Road
London Road was the historic name of Manchester Piccadilly railway station, one of the main rail hubs in Manchester, England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5faf6c8190ba0513be9ae7d128 |
completed | April 29, 2026, 1:22 a.m. |
Created at: April 16, 2026, 8:50 p.m.