Triple
T10940920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tethyan Himalaya |
E258467
|
entity |
| Predicate | fossilContentIncludes |
P9689
|
FINISHED |
| Object | marine invertebrates |
—
|
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: marine invertebrates | Statement: [Tethyan Himalaya, fossilContentIncludes, marine invertebrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilContentIncludes Context triple: [Tethyan Himalaya, fossilContentIncludes, marine invertebrates]
-
A.
fossilContent
Indicates that one entity contains, preserves, or is characterized by the fossils of another entity.
-
B.
fossilGroup
Indicates that one entity is classified as belonging to a particular fossil group or assemblage associated with another entity.
-
C.
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).
-
D.
describedAsFossil
Indicates that something is characterized or identified as a fossil.
-
E.
textsIncludedIn
Indicates that certain texts are contained within, or form a subset of, a larger collection or body of texts.
- 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_69d6aa8769b4819082bfe5e61b9017f0 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770c2821c8190a7b08276c4bfbf33 |
completed | April 9, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69d72e816a98819096d6c10dfb88a66a |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.