Triple
T3502479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maastrichtian |
E73999
|
entity |
| Predicate | importantFossilGroups |
P47321
|
FINISHED |
| Object | dinosaurs |
—
|
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: dinosaurs | Statement: [Maastrichtian, importantFossilGroups, dinosaurs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantFossilGroups Context triple: [Maastrichtian, importantFossilGroups, dinosaurs]
-
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.
fossilSiteType
Indicates the specific type or classification of a site where fossils are found or collected.
-
C.
hasNotableFossilSite
Indicates that an entity contains or is associated with a fossil site recognized as significant or noteworthy.
-
D.
stateFossil
Indicates that a particular fossil has been officially designated as the representative state fossil of a given state.
-
E.
notableSpeciesGroup
chosen
Indicates that an entity is a significant or characteristic member of a particular species group associated with another entity.
- 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_69ad85ce7a9c81909ddc5cf0cb67a6e3 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbbef47988190b5b3fe2e452b9ac8 |
completed | March 8, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69adae0cd8b0819099da300af09880da |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:18 p.m.