Triple
T18677110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Drumheller region |
E456628
|
entity |
| Predicate | hasFossilDeposits |
P117698
|
FINISHED |
| Object | dinosaur fossils |
—
|
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: dinosaur fossils | Statement: [Drumheller region, hasFossilDeposits, dinosaur fossils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFossilDeposits Context triple: [Drumheller region, hasFossilDeposits, dinosaur fossils]
-
A.
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).
-
B.
containsFossilsFrom
Indicates that one entity includes or preserves fossil remains originating from another entity.
-
C.
hasNotableFossilSite
Indicates that an entity contains or is associated with a fossil site recognized as significant or noteworthy.
-
D.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
-
E.
fossilRich
chosen
Indicates that a location, layer, or material contains an abundant or significant concentration of fossils.
- 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_69d8d38f72b4819090a935175d9ca8af |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e556b66680819082a268f1bf857db5 |
completed | April 19, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69e478db7a248190a8c6584673773923 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:48 a.m.