Triple
T21985846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horneophyton lignieri |
E542958
|
entity |
| Predicate | centralStrandType |
P42088
|
FINISHED |
| Object | protostele-like |
—
|
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: protostele-like | Statement: [Horneophyton lignieri, centralStrandType, protostele-like]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralStrandType Context triple: [Horneophyton lignieri, centralStrandType, protostele-like]
-
A.
hasStrand
chosen
Indicates that one entity possesses or is associated with a particular strand or orientation relative to another entity.
-
B.
originalChannelStrand
Indicates that one entity is the original strand or source channel from which another channel or strand is derived or referenced.
-
C.
primaryStructure
Indicates that one entity serves as the main or principal structural component or framework in relation to another entity.
-
D.
chromosomalBand
Indicates a relationship where a specific chromosomal band (a defined region on a chromosome) is associated with or assigned to a chromosome or genomic feature.
-
E.
centralCrossType
Indicates the specific form or design of the cross located at the central position of an object or structure.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12709cb288190a2620e337fea364c |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:04 p.m.