Triple
T12519816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pile O’ Bones |
E299285
|
entity |
| Predicate | reflectsLandscapeFeature |
P61635
|
FINISHED |
| Object | prairie |
—
|
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: prairie | Statement: [Pile O’ Bones, reflectsLandscapeFeature, prairie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsLandscapeFeature Context triple: [Pile O’ Bones, reflectsLandscapeFeature, prairie]
-
A.
hasLandscapeFeatures
Indicates that an entity possesses or includes specific landscape-related characteristics or elements.
-
B.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
C.
surfaceFeatureOf
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
D.
isNaturalFeature
Indicates that the subject is a naturally occurring physical feature of the environment, not created or significantly altered by human activity.
-
E.
sceneFeature
chosen
Indicates a characteristic, element, or attribute that is present within or helps define a particular scene.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d954b867dc8190af8a70f797e4d133 |
completed | April 10, 2026, 7:51 p.m. |
| PD | Predicate disambiguation | batch_69d954096af88190b6be81b008c82139 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 8, 2026, 9:57 p.m.