Triple
T215457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Red Sandstone |
E4810
|
entity |
| Predicate | containsFossilsOf |
P9689
|
FINISHED |
| Object | early terrestrial plants |
—
|
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: early terrestrial plants | Statement: [Old Red Sandstone, containsFossilsOf, early terrestrial plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsFossilsOf Context triple: [Old Red Sandstone, containsFossilsOf, early terrestrial plants]
-
A.
earliestKnownAncestor
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
-
B.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
C.
fauna
Indicates that an entity is an animal or part of the animal life associated with a particular place or context.
-
D.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
E.
geologicalAge
Indicates the time period in Earth's geological history during which an entity (such as a rock, fossil, or formation) originated or was formed.
- F. None of above. chosen
Provenance (4 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25dcba5148190ab80fd14c7cf4bb4 |
completed | Feb. 28, 2026, 3:15 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.