Triple
T26321728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulda River |
E662129
|
entity |
| Predicate | hasCycleRouteAlong |
P151412
|
FINISHED |
| Object | Fulda Cycle Route (Fuldaradweg) |
—
|
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: Fulda Cycle Route (Fuldaradweg) | Statement: [Fulda River, hasCycleRouteAlong, Fulda Cycle Route (Fuldaradweg)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCycleRouteAlong Context triple: [Fulda River, hasCycleRouteAlong, Fulda Cycle Route (Fuldaradweg)]
-
A.
hasAlongRoute
Indicates that one entity lies on or is situated along the path, course, or route taken by another entity.
-
B.
hasNearbyCycleRoute
Indicates that an entity is located close to a designated cycling route or path.
-
C.
isOnCircularRoute
Indicates that an entity follows or belongs to a route that forms a closed loop, starting and ending at the same point.
-
D.
includesRouteBetween
Indicates that one entity (such as a service, plan, or network) contains or provides a specific route connecting two locations or points.
-
E.
routeAlong
chosen
Indicates that one entity follows, runs parallel to, or is situated along the course or path defined by 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60f2bce2881909a81127b9824b3cd |
completed | May 2, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f60b874cc88190a487230abb69efea |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 26, 2026, 10:28 p.m.