Triple
T10017435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toarcian |
E199528
|
entity |
| Predicate | hasTypicalFossils |
P9689
|
FINISHED |
| Object | ammonites |
—
|
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: ammonites | Statement: [Toarcian, hasTypicalFossils, ammonites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalFossils Context triple: [Toarcian, hasTypicalFossils, ammonites]
-
A.
containsFossilsOf
chosen
Indicates that one entity (typically a geological formation, rock, or sample) includes fossil remains or traces belonging to another entity (an organism or taxon).
-
B.
hasFossilEvidence
Indicates that there exists fossil-based evidence supporting the existence, occurrence, or characteristics of the related entity or event.
-
C.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
-
D.
describedAsFossil
Indicates that something is characterized or identified as a fossil.
-
E.
hasNotableFossilSite
Indicates that an entity contains or is associated with a fossil site recognized as significant or noteworthy.
- 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_69ca8315a1a08190ab310f25620f362b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd4c17848190bf1a8017e755ba75 |
completed | April 2, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.