Triple
T104564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosendale cement |
E2110
|
entity |
| Predicate | geologicalSource |
P2856
|
FINISHED |
| Object | dolomitic limestone |
—
|
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: dolomitic limestone | Statement: [Rosendale cement, geologicalSource, dolomitic limestone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalSource Context triple: [Rosendale cement, geologicalSource, dolomitic limestone]
-
A.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
B.
sedimentSource
Indicates that one entity serves as the origin or provider of sediment that is transported to or deposited in another entity.
-
C.
geologicalAge
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
-
D.
naturalResources
chosen
Indicates that one entity possesses, contains, or is a source of natural resources for another entity.
-
E.
seafloorType
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563be81c81908ccc5ed44edd6b8e |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.