Triple
T21985833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horneophyton lignieri |
E542958
|
entity |
| Predicate | vascularSystemComplexity |
P13149
|
FINISHED |
| Object | simple |
—
|
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: simple | Statement: [Horneophyton lignieri, vascularSystemComplexity, simple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vascularSystemComplexity Context triple: [Horneophyton lignieri, vascularSystemComplexity, simple]
-
A.
vascularSystem
Indicates the relationship in which an entity possesses or is associated with a system of blood vessels that transports blood throughout a body.
-
B.
circulationSystem
Indicates that one entity functions as the circulatory system of another, responsible for transporting fluids and related substances throughout it.
-
C.
vascularFeature
chosen
Indicates a relationship where one entity has, exhibits, or is characterized by a particular vascular structure or property.
-
D.
bloodFlowsThrough
Indicates that blood moves within or along the interior of a specified anatomical structure or pathway.
-
E.
venousDrainage
Indicates that one anatomical structure serves as a pathway for venous blood to drain from another structure or region.
- 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.