Triple
T27498759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peace River (Florida) |
E694090
|
entity |
| Predicate | geologicalPeriodFossils |
P123156
|
FINISHED |
| Object | Pliocene |
—
|
NE NERFINISHED |
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: Pliocene | Statement: [Peace River (Florida), geologicalPeriodFossils, Pliocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicalPeriodFossils Context triple: [Peace River (Florida), geologicalPeriodFossils, Pliocene]
-
A.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
-
B.
containsFossilsOf
Indicates that one entity (typically a geological formation, rock, or sample) includes fossil remains or traces belonging to another entity (an organism or taxon).
-
C.
containsFossilsFrom
chosen
Indicates that one entity includes or preserves fossil remains originating from another entity.
-
D.
fossilDistribution
Indicates the geographic or stratigraphic locations where fossils of an organism or taxon have been found.
-
E.
fossilRecordType
Indicates the classification of how a fossil is preserved or represented in the geological record (e.g., body fossil, trace fossil, cast, mold).
- 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_69ef538370888190b1ddf53bb4831188 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ec0c9888190a7f0de2aa4d1d0b1 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:10 p.m.