Triple
T37199377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Block of Discord |
E921685
|
entity |
| Predicate | locatedOnSideOfStreet |
P31095
|
FINISHED |
| Object | east side of Passeig de Gràcia |
—
|
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: east side of Passeig de Gràcia | Statement: [Block of Discord, locatedOnSideOfStreet, east side of Passeig de Gràcia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSideOfStreet Context triple: [Block of Discord, locatedOnSideOfStreet, east side of Passeig de Gràcia]
-
A.
situatedOnSideOf
chosen
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
B.
isSideStreetOf
Indicates that one street is a smaller, less prominent road that connects to or branches off from another main street.
-
C.
locationSide
Indicates that one entity is positioned on a particular side (e.g., left, right, front, back) relative to another entity or reference point.
-
D.
locatedBetweenStreets
Indicates that something is situated between two specified streets, with its position bounded or defined by those streets.
-
E.
hasSideStreetRole
Indicates that an entity holds a specific functional or contextual role in relation to a side street.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.