Triple
T27826444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allegany Plateau |
E702964
|
entity |
| Predicate | hasGeologicComposition |
P89872
|
FINISHED |
| Object | sedimentary rock |
—
|
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: sedimentary rock | Statement: [Allegany Plateau, hasGeologicComposition, sedimentary rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeologicComposition Context triple: [Allegany Plateau, hasGeologicComposition, sedimentary rock]
-
A.
hasGeologicalNature
chosen
Indicates that something possesses a specific geological character, composition, or formation type.
-
B.
hasGeologicResource
Indicates that an entity possesses, contains, or is associated with a particular geologic resource.
-
C.
hasMagmaComposition
Indicates that something possesses or is characterized by a specific magma composition.
-
D.
hasGeologicalUnit
Indicates that an entity is associated with or contains a specific geological unit, such as a rock layer, formation, or stratigraphic unit.
-
E.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 27, 2026, 5:52 p.m.