Triple
T30875231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vendobionta |
E786457
|
entity |
| Predicate | basedOnEvidenceType |
P93688
|
FINISHED |
| Object | impression fossils |
—
|
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: impression fossils | Statement: [Vendobionta, basedOnEvidenceType, impression fossils]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnEvidenceType Context triple: [Vendobionta, basedOnEvidenceType, impression fossils]
-
A.
evidenceTypeHandled
Indicates that an entity is responsible for processing or managing a particular type or category of evidence.
-
B.
usedEvidenceType
Indicates that a particular type or category of evidence was employed or relied upon in a given context or activity.
-
C.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
D.
basedOnType
chosen
Indicates that one entity is derived, determined, or classified according to the type or category of another entity.
-
E.
evidenceEvaluation
Indicates the assessment or judgment of the quality, relevance, or strength of given evidence in relation to a claim or conclusion.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: April 29, 2026, 8:48 p.m.