Triple
T19676071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palaeocastor |
E472454
|
entity |
| Predicate | traceFossilsInclude |
P87251
|
FINISHED |
| Object | burrow systems |
—
|
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: burrow systems | Statement: [Palaeocastor, traceFossilsInclude, burrow systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traceFossilsInclude Context triple: [Palaeocastor, traceFossilsInclude, burrow systems]
-
A.
traceFossils
chosen
Indicates evidence of an organism’s activity or behavior preserved in the geological record, rather than the organism’s physical remains.
-
B.
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).
-
C.
containsFossilsFrom
Indicates that one entity includes or preserves fossil remains originating from another entity.
-
D.
includesFossilSpecies
Indicates that one entity (such as a collection, site, or layer) contains or encompasses one or more fossil species as part of its contents or composition.
-
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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bbea8c8190b0ad841d95068e0e |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.