Triple
T7575588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dinosauria |
E179354
|
entity |
| Predicate | fossilsFoundOn |
P77558
|
FINISHED |
| Object | all continents |
—
|
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: all continents | Statement: [Dinosauria, fossilsFoundOn, all continents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilsFoundOn Context triple: [Dinosauria, fossilsFoundOn, all continents]
-
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.
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.
-
C.
fossilGroup
Indicates that one entity is classified as belonging to a particular fossil group or assemblage associated with another entity.
-
D.
stateFossil
Indicates that a particular fossil has been officially designated as the representative state fossil of a given state.
-
E.
fossilSiteType
Indicates the specific type or classification of a site where fossils are found or collected.
- F. None of above. chosen
Provenance (4 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_69c69f316e50819081a271c85c06f918 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f94a25148190b5b76e000e0336c4 |
completed | March 27, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69c6f4de77048190b8769e717fdcf8e7 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f5b1a6a08190b9ff2bc8a7befe0d |
completed | March 27, 2026, 9:25 p.m. |
Created at: March 27, 2026, 3:51 p.m.