Triple
T11032484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double O Arch |
E260789
|
entity |
| Predicate | visitorGuideline |
P97399
|
FINISHED |
| Object | stay on designated trails |
—
|
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: stay on designated trails | Statement: [Double O Arch, visitorGuideline, stay on designated trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorGuideline Context triple: [Double O Arch, visitorGuideline, stay on designated trails]
-
A.
visitorInformation
Indicates that information or details are provided for or about visitors in relation to a particular place, service, or event.
-
B.
visitorCenter
Indicates that a location serves as a visitor center for a place, providing information or services to visitors of that place.
-
C.
visitorPractice
Indicates that a visitor engages in or performs a particular practice, activity, or routine.
-
D.
visitorRequirement
Indicates the conditions or criteria that must be met by a visitor in order to be allowed or accepted.
-
E.
visitorManagement
Indicates the management, tracking, and control of visitors’ access, activities, and permissions within a location or system.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e650b48190967c53f54e3464ad |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:25 p.m.