Triple
T21955108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louvain-la-Neuve |
E542166
|
entity |
| Predicate | transportModePriority |
P64592
|
FINISHED |
| Object | pedestrian |
—
|
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: pedestrian | Statement: [Louvain-la-Neuve, transportModePriority, pedestrian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModePriority Context triple: [Louvain-la-Neuve, transportModePriority, pedestrian]
-
A.
transportPriority
Indicates that one entity is assigned a higher or specific level of precedence over others in being transported or moved.
-
B.
transportModeImportant
chosen
Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
-
C.
transportModeTo
Indicates the means or mode of transportation used to travel to a specified destination.
-
D.
transportModeComparedWith
Indicates a comparison between two entities regarding the mode of transport they use or are associated with.
-
E.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
- 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_69e0c47ef0e48190a50e1bcc43f4b3fd |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1243f46dc819097e4a1849af7fba4 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:59 p.m.