Triple
T25077151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Rock Cave |
E628080
|
entity |
| Predicate | artifactTypeFound |
P157618
|
FINISHED |
| Object | sagebrush-bark sandals |
—
|
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: sagebrush-bark sandals | Statement: [Fort Rock Cave, artifactTypeFound, sagebrush-bark sandals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artifactTypeFound Context triple: [Fort Rock Cave, artifactTypeFound, sagebrush-bark sandals]
-
A.
artifactType
Indicates the specific kind or category of artifact that an entity is classified as.
-
B.
discoveredArtifact
Indicates that an entity has found or uncovered a previously unknown or hidden artifact.
-
C.
artifact
Indicates that one entity is an artifact created, modified, or used by another entity.
-
D.
featuresArtifactsFrom
Indicates that one entity includes, presents, or showcases artifacts that originate from or are associated with another entity.
-
E.
featuresArtifact
Indicates that one entity prominently includes, presents, or showcases another entity as an artifact.
- 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_69e2ff2e73f881909992bf3eda5c25cb |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f45d1ad0ec8190831b9d6d28a6644a |
completed | May 1, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:21 a.m.