Triple
T32695315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mile-Ex |
E835989
|
entity |
| Predicate | streetGridRoughlyBoundedBy |
P174803
|
FINISHED |
| Object | Avenue du Parc |
—
|
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: Avenue du Parc | Statement: [Mile-Ex, streetGridRoughlyBoundedBy, Avenue du Parc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetGridRoughlyBoundedBy Context triple: [Mile-Ex, streetGridRoughlyBoundedBy, Avenue du Parc]
-
A.
streetGridRange
Indicates the span or extent of a street segment within a defined grid or block range in a street network.
-
B.
streetGridExtendedFrom
Indicates that one street grid layout continues or expands outward from another street grid as its extension.
-
C.
locatedBetweenStreets
Indicates that something is situated between two specified streets, with its position bounded or defined by those streets.
-
D.
citySquareBordered
Indicates that a city square is directly bordered or enclosed along its edges by another spatial feature or area.
-
E.
avenueBoundaryEast
Indicates that something serves as the eastern boundary or edge of an avenue.
- F. None of above. chosen
Provenance (4 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_69f3493323288190a4e88251035fe96e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c81cd47c8190b3b8d476327688b8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:10 a.m.