Triple
T28817400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Davoei Zone |
E727675
|
entity |
| Predicate | correlationTool |
P28584
|
FINISHED |
| Object | ammonite zonation |
—
|
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: ammonite zonation | Statement: [Davoei Zone, correlationTool, ammonite zonation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: correlationTool Context triple: [Davoei Zone, correlationTool, ammonite zonation]
-
A.
dataCorrelatedAt
Indicates that two or more data sets or variables exhibit a statistical correlation at a specified time, context, or granularity.
-
B.
spatialCorrelation
Indicates a relationship where two spatial variables or patterns vary together in a statistically related way across space.
-
C.
hasCorrelationFunctions
Indicates that there exist correlation functions characterizing statistical or relational dependencies between the associated entities.
-
D.
correlatorType
Indicates the specific kind or category of correlator used to establish or analyze a correlation between entities or signals.
-
E.
relatedTool
chosen
Indicates that one tool has a meaningful association or connection with another tool, such as being complementary, compatible, or commonly used together.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 28, 2026, 6:33 a.m.