Triple
T35535571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Premužić Trail |
E1026921
|
entity |
| Predicate | hasRouteMarkers |
P37949
|
FINISHED |
| Object | hiking waymarks |
—
|
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: hiking waymarks | Statement: [Premužić Trail, hasRouteMarkers, hiking waymarks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRouteMarkers Context triple: [Premužić Trail, hasRouteMarkers, hiking waymarks]
-
A.
usesRouteMarkers
Indicates that an entity follows or relies on designated route markers to navigate or traverse a path.
-
B.
hasRouteMaps
Indicates that one entity possesses or provides route maps that describe paths, directions, or connections related to another entity.
-
C.
hasMarker
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
D.
hasSignpostedRoute
Indicates that there is a formally marked or signposted route connecting or passing through the related entities.
-
E.
hasRouteFeature
chosen
Indicates that a route possesses or is associated with a specific characteristic, attribute, or feature.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe9fb9735c8190a360b556c9d00b3f |
completed | May 9, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69fe9eaa88008190a9b2a469dc685002 |
completed | May 9, 2026, 2:40 a.m. |
Created at: May 3, 2026, 4:04 p.m.