Triple
T12335193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Rive Gauche district |
E294064
|
entity |
| Predicate | hasPublicSpacePolicy |
P104554
|
FINISHED |
| Object | priority to pedestrians |
—
|
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: priority to pedestrians | Statement: [Paris Rive Gauche district, hasPublicSpacePolicy, priority to pedestrians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPublicSpacePolicy Context triple: [Paris Rive Gauche district, hasPublicSpacePolicy, priority to pedestrians]
-
A.
hasPublicSpaces
Indicates that an entity includes or provides areas that are accessible and usable by the general public.
-
B.
hasPublicSpaceRole
Indicates that an entity holds a specific role, function, or responsibility within a public space.
-
C.
hasPublicSpaceAlong
Indicates that a public space (such as a park, plaza, or walkway) is located adjacent to or runs alongside the referenced feature or element.
-
D.
isInPublicSpace
Indicates that an entity is located within a space that is publicly accessible or open to the general public.
-
E.
openSpacePolicy
Indicates that an entity has a policy allowing open, flexible, or unrestricted use of a space or area.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f6683e881908920e1fee02a14e3 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ecb5efc819086a3530282278bb1 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.