Triple
T21151547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Place des Petits-Pères |
E521202
|
entity |
| Predicate | hasNearbyUrbanFeature |
P44123
|
FINISHED |
| Object | Rue Notre-Dame-des-Victoires |
—
|
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: Rue Notre-Dame-des-Victoires | Statement: [Place des Petits-Pères, hasNearbyUrbanFeature, Rue Notre-Dame-des-Victoires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyUrbanFeature Context triple: [Place des Petits-Pères, hasNearbyUrbanFeature, Rue Notre-Dame-des-Victoires]
-
A.
nearbyUrbanCenter
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
B.
hasUrbanProximity
chosen
Indicates that one entity is located near or within easy access to an urban area associated with another entity.
-
C.
hasNearbyLandUse
Indicates that one land area is located close to another area characterized by a specific type of land use.
-
D.
hasUndergroundFeatureNearby
Indicates that an entity is located close to an underground feature (such as a tunnel, cave, or buried structure).
-
E.
hasNearbyCityFunction
Indicates that one entity serves as a nearby urban center or city-like service hub for another entity.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72401830c8190a2008c40c4174d97 |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.