Triple
T28088785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corrientes 1300–1500 theater district |
E709898
|
entity |
| Predicate | streetNumberRange |
P24400
|
FINISHED |
| Object | 1300–1500 |
—
|
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: 1300–1500 | Statement: [Corrientes 1300–1500 theater district, streetNumberRange, 1300–1500]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetNumberRange Context triple: [Corrientes 1300–1500 theater district, streetNumberRange, 1300–1500]
-
A.
roadNumberRange
Indicates that a road is identified by a continuous range of road numbers between a specified minimum and maximum.
-
B.
streetAddressRange
chosen
Indicates the span of street address numbers (e.g., from a minimum to a maximum) that are associated with a particular street segment or location.
-
C.
postalCodeRange
Indicates that one entity specifies a contiguous range of postal codes applicable to another entity or context.
-
D.
RVNumberRange
Indicates that a recreational vehicle’s number or identifier falls within a specified numeric range.
-
E.
streetGridRange
Indicates the span or extent of a street segment within a defined grid or block range in a street network.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 8:57 p.m.