Triple
T28036631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-Dig Fossils area |
E708425
|
entity |
| Predicate | visitorCan |
P32554
|
FINISHED |
| Object | dig for fossils |
—
|
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: dig for fossils | Statement: [U-Dig Fossils area, visitorCan, dig for fossils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitorCan Context triple: [U-Dig Fossils area, visitorCan, dig for fossils]
-
A.
visitorIs
Indicates that one entity is acting in the role or capacity of a visitor with respect to another entity.
-
B.
visitorUse
Indicates that an entity is being used, accessed, or engaged with by a visitor or temporary user.
-
C.
visitorStatus
Indicates the current state or condition of an entity in its role as a visitor (e.g., whether they are active, pending, past, or otherwise classified in their visit).
-
D.
canVisit
chosen
Indicates that one entity is permitted or able to go to or access another entity or location.
-
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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:21 p.m.