Triple
T37535982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diplodocidae |
E933194
|
entity |
| Predicate | fossilTypeLocalityRegion |
P117889
|
FINISHED |
| Object | Morrison Formation |
—
|
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: Morrison Formation | Statement: [Diplodocidae, fossilTypeLocalityRegion, Morrison Formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilTypeLocalityRegion Context triple: [Diplodocidae, fossilTypeLocalityRegion, Morrison Formation]
-
A.
fossilTypeLocality
Indicates the specific locality that serves as the reference site where the defining fossil specimen(s) of a particular fossil type were originally found.
-
B.
fossilsFoundAt
Indicates that fossil remains of an organism or taxon have been discovered at a particular location or site.
-
C.
fossilDistribution
chosen
Indicates the geographic or stratigraphic locations where fossils of an organism or taxon have been found.
-
D.
fossilSiteType
Indicates the specific type or classification of a site where fossils are found or collected.
-
E.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.