Triple
T19068073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohrid boardwalk and port |
E466717
|
entity |
| Predicate | offersTransport |
P112787
|
FINISHED |
| Object | boat tours on Lake Ohrid |
—
|
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: boat tours on Lake Ohrid | Statement: [Ohrid boardwalk and port, offersTransport, boat tours on Lake Ohrid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersTransport Context triple: [Ohrid boardwalk and port, offersTransport, boat tours on Lake Ohrid]
-
A.
offersVehicleTransport
chosen
Indicates that one entity provides or makes available transportation services using a vehicle to another entity.
-
B.
offersFootPassengerTravel
Indicates that an entity provides transportation services specifically for passengers traveling on foot, without vehicles.
-
C.
offersDestination
Indicates that one entity provides or makes available another entity as a possible destination.
-
D.
transportOptions
Indicates the available means or methods by which something or someone can be transported from one place to another.
-
E.
transports
Indicates that one entity carries or conveys another entity from one place to another.
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19b94d08190865b62d98f718bb0 |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.