Triple
T30994553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leptotragulus |
E789758
|
entity |
| Predicate | foundInFossilRecordOf |
P170999
|
FINISHED |
| Object | United States |
—
|
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: United States | Statement: [Leptotragulus, foundInFossilRecordOf, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInFossilRecordOf Context triple: [Leptotragulus, foundInFossilRecordOf, United States]
-
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.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
-
C.
knownFromFossils
chosen
Indicates that the existence or occurrence of something is inferred or established based on fossil evidence.
-
D.
containsFossilsFrom
Indicates that one entity includes or preserves fossil remains originating from another entity.
-
E.
geologicalPeriodFossils
Indicates that a particular geological period is characterized or evidenced by the presence of specific fossils.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: April 29, 2026, 8:56 p.m.