Triple
T34864777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jánošíkove diery |
E1004980
|
entity |
| Predicate | approximateVisitDuration |
P110283
|
FINISHED |
| Object | 2–5 hours |
—
|
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: 2–5 hours | Statement: [Jánošíkove diery, approximateVisitDuration, 2–5 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateVisitDuration Context triple: [Jánošíkove diery, approximateVisitDuration, 2–5 hours]
-
A.
hasTypicalVisitDuration
chosen
Indicates the usual or expected length of time that a visit to something typically lasts.
-
B.
approximateTripDuration
Indicates the estimated length of time required to complete a trip between specified locations or points in a journey.
-
C.
commonDuration
Indicates that two or more events, actions, or states share the same length of time.
-
D.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
E.
approximateViewingLength
Indicates the estimated duration of time that something is expected to be viewed or watched.
- 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
Created at: May 3, 2026, 4 p.m.