Triple
T14435270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calle Morandé |
E357942
|
entity |
| Predicate | streetNumberOfHistoricEntrance |
P40967
|
FINISHED |
| Object | 80 |
—
|
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: 80 | Statement: [Calle Morandé, streetNumberOfHistoricEntrance, 80]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetNumberOfHistoricEntrance Context triple: [Calle Morandé, streetNumberOfHistoricEntrance, 80]
-
A.
boroughNumber
Indicates the numerical identifier assigned to a specific borough within a larger administrative or municipal division.
-
B.
hasHistoricStreet
Indicates that an entity is associated with or located on a street that has recognized historical significance.
-
C.
isNumberedAvenueOf
Indicates that one entity is an avenue identified by a numerical designation that belongs to or is part of the other entity (such as a city or road network).
-
D.
isNumberedStreet
Indicates that a street is designated primarily by a number (e.g., "1st Street," "42nd Avenue") rather than by a proper name.
-
E.
houseNumber
chosen
Indicates that an entity has a specific house or street number as part of its address.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de9148cf4481909082cc91b2f76218 |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.