Triple
T19364386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Brunswick sandstone |
E484362
|
entity |
| Predicate | foundInGeologicUnit |
P19734
|
FINISHED |
| Object | Newark Basin sandstones |
—
|
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: Newark Basin sandstones | Statement: [New Brunswick sandstone, foundInGeologicUnit, Newark Basin sandstones]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInGeologicUnit Context triple: [New Brunswick sandstone, foundInGeologicUnit, Newark Basin sandstones]
-
A.
foundInGeologicSetting
chosen
Indicates that something occurs, is present, or has been discovered within a particular geological environment or context.
-
B.
geologicUnitOf
Indicates that one entity is a geologic unit to which the other entity belongs or with which it is associated.
-
C.
hasGeologicalUnit
Indicates that an entity is associated with or contains a specific geological unit, such as a rock layer, formation, or stratigraphic unit.
-
D.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
E.
foundInStructure
Indicates that an entity is located within, contained by, or structurally part of another entity or structure.
- 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_69d8e8d305088190ad13571532aa454c |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e619a9ac68819082cf9deadf526156 |
completed | April 20, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.