Triple
T12127842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spider Cave |
E288853
|
entity |
| Predicate | visitorImpactPolicy |
P97399
|
FINISHED |
| Object | leave no trace |
—
|
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: leave no trace | Statement: [Spider Cave, visitorImpactPolicy, leave no trace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorImpactPolicy Context triple: [Spider Cave, visitorImpactPolicy, leave no trace]
-
A.
visitorGuideline
chosen
Indicates guidelines or rules that specify how visitors are expected or allowed to behave or proceed in a particular context.
-
B.
visitorManagement
Indicates the management, tracking, and control of visitors’ access, activities, and permissions within a location or system.
-
C.
boardingPolicy
Indicates the rules or procedures governing how and in what order passengers are allowed to board a vehicle or vessel.
-
D.
visitorUse
Indicates that an entity is being used, accessed, or engaged with by a visitor or temporary user.
-
E.
visitorAccessibility
Indicates how easily or suitably a place, service, or resource can be used or reached by visitors, including those with varying needs or abilities.
- 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_69d6ab4b5e4c81909950b17151eb0951 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91841615c819097f20a7447a1b8f4 |
completed | April 10, 2026, 3:33 p.m. |
| PD | Predicate disambiguation | batch_69d91508f8008190b3a90ec0bf0953ca |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:49 p.m.