Triple
T391146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tracheophyta |
E8882
|
entity |
| Predicate | evolved |
P1245
|
FINISHED |
| Object | in Silurian period |
—
|
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: in Silurian period | Statement: [Tracheophyta, evolved, in Silurian period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evolved Context triple: [Tracheophyta, evolved, in Silurian period]
-
A.
developed
Indicates that one entity created, designed, or brought another entity into a more advanced or complete state through effort or work.
-
B.
futureEvolution
Indicates a predicted or potential future development or transformation of one entity into another.
-
C.
emergedFrom
Indicates that one entity originated, arose, or came forth from another entity or source.
-
D.
developedFrom
chosen
Indicates that one entity originates, evolves, or is derived from another as its source or precursor.
-
E.
emergedWith
Indicates that one entity came forth, appeared, or became visible at the same time and in association with another entity.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec5d73e881909101308a583c8f13 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e96960608190bdd342da9c5ddb5e |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.