Triple
T25180518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grimes Graves |
E630569
|
entity |
| Predicate | hasPubliclyAccessibleShaft |
P160902
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Grimes Graves, hasPubliclyAccessibleShaft, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPubliclyAccessibleShaft Context triple: [Grimes Graves, hasPubliclyAccessibleShaft, true]
-
A.
hasPrimaryAccessShaft
Indicates that one entity serves as the main access shaft associated with another entity.
-
B.
hasShafts
Indicates that one entity possesses or is equipped with one or more shafts as components or structural elements.
-
C.
typicalShaftType
Indicates the usual or characteristic type of shaft associated with an entity or configuration.
-
D.
hasBoltHandle
Indicates that one entity is equipped with or includes a bolt-style handle associated with another entity.
-
E.
shaftOrientation
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f60cd7b3e88190a1206958c0f0b225 |
completed | May 2, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f60c32ce088190a620eb59d2499fa9 |
completed | May 2, 2026, 2:37 p.m. |
Created at: April 21, 2026, 12:35 p.m.