Triple
T11765996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Permian Garber Sandstone |
E279782
|
entity |
| Predicate | hostRockFor |
P53497
|
FINISHED |
| Object | barite rose rocks |
—
|
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: barite rose rocks | Statement: [Permian Garber Sandstone, hostRockFor, barite rose rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostRockFor Context triple: [Permian Garber Sandstone, hostRockFor, barite rose rocks]
-
A.
hostRock
chosen
Indicates that one rock body serves as the surrounding or enclosing rock in which another geological feature (such as an ore deposit, vein, or intrusion) occurs.
-
B.
hostPark
Indicates that an entity provides space or facilities for a park to be located or held within its area.
-
C.
hostStar
Indicates that one celestial object serves as the primary star around which another object, such as a planet or system, is associated or orbits.
-
D.
host
Indicates that one entity provides space, resources, or services to accommodate, receive, or entertain another entity.
-
E.
hostRepublic
Indicates that an entity serves as the host country or republic for another entity or event.
- 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_69d6ab01d2688190ad8ed6bda487eaa5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a8c2e8b08190a31b1e284fca2aee |
completed | April 10, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69d8a242cd8c819086ed6c5f292dc8cb |
completed | April 10, 2026, 7:09 a.m. |
Created at: April 8, 2026, 9:41 p.m.