Triple
T31930544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinosaur Provincial Park |
E815233
|
entity |
| Predicate | numberOfDinosaurSpeciesDescribedFromSite |
P6211
|
FINISHED |
| Object | more than 40 |
—
|
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: more than 40 | Statement: [Dinosaur Provincial Park, numberOfDinosaurSpeciesDescribedFromSite, more than 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfDinosaurSpeciesDescribedFromSite Context triple: [Dinosaur Provincial Park, numberOfDinosaurSpeciesDescribedFromSite, more than 40]
-
A.
hasApproximateNumberOfFossils
Indicates that an entity is associated with an estimated or approximate count of fossils, rather than an exact number.
-
B.
discoveredAsFossilSite
Indicates that a location was identified and recognized as a site containing fossils.
-
C.
numberOfSpecies
chosen
Indicates the count of distinct species associated with a given entity or context.
-
D.
speciesNumber
Indicates the numerical identifier or count associated with a particular species in a given context.
-
E.
fossilSiteType
Indicates the specific type or classification of a site where fossils are found or collected.
- 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a015ff02814819094806517fc4c69fa |
completed | May 11, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_6a0154ddd3c48190b85f9f48731cfd8f |
completed | May 11, 2026, 4:02 a.m. |
Created at: May 1, 2026, 12:04 a.m.