Triple
T11837050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stegosaurus |
E281543
|
entity |
| Predicate | nationalFossil |
P101778
|
FINISHED |
| Object | state fossil of Colorado |
—
|
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: state fossil of Colorado | Statement: [Stegosaurus, nationalFossil, state fossil of Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nationalFossil Context triple: [Stegosaurus, nationalFossil, state fossil of Colorado]
-
A.
stateFossil
Indicates that a particular fossil has been officially designated as the representative state fossil of a given state.
-
B.
countryFossilsFound
Indicates that fossils have been discovered within the geographic boundaries of a given country.
-
C.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
-
D.
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).
-
E.
fossilDiscoverer
Indicates the relationship in which an agent is the one who discovered or unearthed a particular fossil.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62fec0881908c7b89c0b5bcc9a2 |
completed | April 10, 2026, 7:26 a.m. |
| PD | Predicate disambiguation | batch_69d8a254a57481908a1e6ad97919c416 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.