Triple
T2879021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GR11 long-distance footpath |
E56949
|
entity |
| Predicate | waymarkedAs |
P1777
|
FINISHED |
| Object | red and white stripes |
—
|
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: red and white stripes | Statement: [GR11 long-distance footpath, waymarkedAs, red and white stripes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waymarkedAs Context triple: [GR11 long-distance footpath, waymarkedAs, red and white stripes]
-
A.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
B.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
C.
routeBetween
Indicates that there exists a path or connection enabling travel or communication between two locations or points.
-
D.
roadTraverses
Indicates that a road passes through, crosses, or extends across a specified geographic area or feature.
-
E.
roadFeature
chosen
Indicates that an entity is a specific physical or functional characteristic associated with a road, such as its structure, markings, or related infrastructure.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe008925c81909683d0ebc6227e5e |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.