Triple
T21323398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rue de la Liberté |
E525681
|
entity |
| Predicate | hasPedestrianFlow |
P19607
|
FINISHED |
| Object | high foot traffic |
—
|
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: high foot traffic | Statement: [Rue de la Liberté, hasPedestrianFlow, high foot traffic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedestrianFlow Context triple: [Rue de la Liberté, hasPedestrianFlow, high foot traffic]
-
A.
hasPedestrianTrafficLevel
chosen
Indicates the level or intensity of pedestrian traffic associated with a given location or pathway.
-
B.
hasPedestrianFunction
Indicates that an entity serves a role, purpose, or function specifically related to pedestrians or pedestrian use.
-
C.
hasPedestrianEnvironment
Indicates that a location or area provides facilities, conditions, or features suitable for pedestrian use and movement.
-
D.
hasPedestrianSteps
Indicates that one location or structure is connected to another by pedestrian steps or stairways.
-
E.
hasPedestrianAccessTo
Indicates that a location or area can be reached or entered safely and directly by people on foot.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ed572548190bd71ef690fc7befe |
completed | April 21, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:40 p.m.