Triple
T17086617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thelodonti |
E414614
|
entity |
| Predicate | geologicalDeposits |
P68054
|
FINISHED |
| Object | Silurian marine sediments |
—
|
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: Silurian marine sediments | Statement: [Thelodonti, geologicalDeposits, Silurian marine sediments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalDeposits Context triple: [Thelodonti, geologicalDeposits, Silurian marine sediments]
-
A.
economicGeology
Indicates a relationship where geological features, materials, or processes are studied or evaluated in terms of their economic value, such as for resource exploration, extraction, or utilization.
-
B.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
C.
hasGeologicResource
chosen
Indicates that an entity possesses, contains, or is associated with a particular geologic resource.
-
D.
saltDepositsOrigin
Indicates the geological source or formation process from which salt deposits originate.
-
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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbe7ccb48190b8fb39e2a0ba0782 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.