Triple
T13544956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesa Top Loop Road sites |
E323485
|
entity |
| Predicate | hasTypicalVisitDuration |
P110283
|
FINISHED |
| Object | 1 to 2 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: 1 to 2 hours | Statement: [Mesa Top Loop Road sites, hasTypicalVisitDuration, 1 to 2 hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalVisitDuration Context triple: [Mesa Top Loop Road sites, hasTypicalVisitDuration, 1 to 2 hours]
-
A.
hasTypicalPerformanceDuration
Indicates the usual or expected length of time that a performance or activity typically lasts.
-
B.
typicalVisitType
Indicates the usual or most common category of visit associated with an entity or event.
-
C.
hasTypicalEastboundDurationHours
Indicates the usual number of hours it takes for something (such as a trip or process) to be completed when moving or proceeding eastbound.
-
D.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
E.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
- F. None of above. chosen
Provenance (4 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbbb8c77dc8190b7bd803b5e168d23 |
completed | April 12, 2026, 3:34 p.m. |
Created at: April 9, 2026, 9:45 p.m.