Triple
T29190330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Varykino retreat |
E739971
|
entity |
| Predicate | travelMethodToReach |
P117172
|
FINISHED |
| Object | lake transport |
—
|
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: lake transport | Statement: [Varykino retreat, travelMethodToReach, lake transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelMethodToReach Context triple: [Varykino retreat, travelMethodToReach, lake transport]
-
A.
transportModeTo
chosen
Indicates the means or mode of transportation used to travel to a specified destination.
-
B.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
-
C.
mobilityMethod
Indicates the means or method by which an entity moves or is transported from one place to another.
-
D.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
E.
transportationFunction
Indicates that one entity serves to move or carry 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_69f07cb8033c8190b8807e219a14333d |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f68a16debc8190a12f5f65ced055d7 |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f6860def1c81909d79e1f088c4b5e5 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 28, 2026, 12:02 p.m.