Triple
T22281724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rydal Caves |
E550747
|
entity |
| Predicate | hasApproximateVisitDuration |
P4874
|
FINISHED |
| Object | short visit |
—
|
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: short visit | Statement: [Rydal Caves, hasApproximateVisitDuration, short visit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateVisitDuration Context triple: [Rydal Caves, hasApproximateVisitDuration, short visit]
-
A.
hasTypicalVisitDuration
Indicates the usual or expected length of time that a visit to something typically lasts.
-
B.
hasApproximateDuration
chosen
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
C.
hasVisitingTime
Indicates that there is a specified time period during which visits are allowed or scheduled for an entity.
-
D.
hasRevisitTime
Indicates the interval or schedule at which an entity is revisited, repeated, or observed again.
-
E.
bestVisitedAt
Indicates the optimal time or conditions under which a place or entity should be visited.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f14eac0994819088e39a1b5d39cf18 |
completed | April 29, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.