Triple
T13984610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coulée verte cycle path |
E336404
|
entity |
| Predicate | landscaped |
P13651
|
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: [Coulée verte cycle path, landscaped, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landscaped Context triple: [Coulée verte cycle path, landscaped, true]
-
A.
landscapeDesignedBy
Indicates that a particular landscape or outdoor environment was planned, created, or shaped by a specific designer or design entity.
-
B.
landscapeElement
Indicates that one entity functions as a landscape-related feature or component in relation to another entity.
-
C.
hasLandscaping
chosen
Indicates that an entity possesses or is associated with designed outdoor grounds or landscape features.
-
D.
landscapeManagement
Indicates the planning, implementation, and maintenance of actions that shape, conserve, or restore the physical and ecological characteristics of a landscape.
-
E.
landscapeType
Indicates the kind or category of natural terrain or scenery that characterizes a place or area.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea3e5a081908ed8ead108139252 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.