Triple
T30744191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dent site |
E782772
|
entity |
| Predicate | faunalRemains |
P9689
|
FINISHED |
| Object | Columbian mammoth |
—
|
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: Columbian mammoth | Statement: [Dent site, faunalRemains, Columbian mammoth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faunalRemains Context triple: [Dent site, faunalRemains, Columbian mammoth]
-
A.
fossilMorphology
Indicates that one entity describes or characterizes the physical form and structural features of a fossil associated with another entity.
-
B.
containsFossilsOf
chosen
Indicates that one entity (typically a geological formation, rock, or sample) includes fossil remains or traces belonging to another entity (an organism or taxon).
-
C.
evidenceOfCarnivoreActivityOnBones
Indicates that the bones show signs or traces of carnivore activity, such as gnawing, tooth marks, or other feeding-related modifications.
-
D.
discoveredRemainsIn
Indicates that one entity found or uncovered the physical remains of another entity at a specific location.
-
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_69f224aeb1588190897d395e8ed2acb8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f6b835c8190b52471f03ebf3453 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:38 p.m.