Triple
T18817561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whin Sill dolerite |
E460176
|
entity |
| Predicate | rockClass |
P1326
|
FINISHED |
| Object | mafic igneous 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: mafic igneous rock | Statement: [Whin Sill dolerite, rockClass, mafic igneous rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rockClass Context triple: [Whin Sill dolerite, rockClass, mafic igneous rock]
-
A.
rockUnit
Indicates a relationship where an entity is classified as, or associated with, a particular geological rock unit.
-
B.
rockEra
Indicates that an entity is associated with, belongs to, or occurs during the rock music era.
-
C.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
D.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
-
E.
reservoirRock
Indicates that one entity functions as a porous and permeable rock formation capable of storing and transmitting fluids (such as hydrocarbons or water) for another entity.
- 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_69d8dcf94c288190a06dea029ae4b223 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5a6b7e75c81909bc65cfc61cbe1c6 |
completed | April 20, 2026, 4:08 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:55 a.m.