Triple
T21746068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crest de Saint-Amand |
E536789
|
entity |
| Predicate | accessActivity |
P100988
|
FINISHED |
| Object | hiking approach required |
—
|
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: hiking approach required | Statement: [Crest de Saint-Amand, accessActivity, hiking approach required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessActivity Context triple: [Crest de Saint-Amand, accessActivity, hiking approach required]
-
A.
accessIs
Indicates that one entity has the ability, permission, or means to reach, use, or interact with another entity or resource.
-
B.
accessStatus
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
C.
accessFeature
Indicates that one entity is permitted to use or interact with a specific feature or capability of another entity.
-
D.
accessMission
Indicates that an entity is permitted to enter, use, or interact with a specific mission or mission-related resources.
-
E.
hasAccessActivity
chosen
Indicates that an entity performs, records, or is involved in an activity related to accessing a resource, system, or location.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a76540c8190b91a67f4a70869fb |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.