Triple
T22603589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenue de la Tour-Maubourg (left bank access) |
E574894
|
entity |
| Predicate | isRiversideThoroughfare |
P47954
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Avenue de la Tour-Maubourg (left bank access), isRiversideThoroughfare, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRiversideThoroughfare Context triple: [Avenue de la Tour-Maubourg (left bank access), isRiversideThoroughfare, true]
-
A.
isRiverside
Indicates that one entity is located beside or along the bank of a river in relation to another entity.
-
B.
isRiversideRangeOf
Indicates that something is a range or stretch of land that lies along the side of a river.
-
C.
isInnerCityRoad
Indicates that a road is located within and primarily serves the inner (central, densely built-up) area of a city.
-
D.
isWaterfrontThoroughfare
chosen
Indicates that a thoroughfare (such as a road, street, or path) is located directly along or adjacent to a body of water.
-
E.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1626fad6881909895cc8c0af62f0d |
completed | April 29, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:51 p.m.