Triple
T33216923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thyrsopteridaceae |
E850313
|
entity |
| Predicate | sorusPosition |
P176210
|
FINISHED |
| Object | abaxial side of fronds |
—
|
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: abaxial side of fronds | Statement: [Thyrsopteridaceae, sorusPosition, abaxial side of fronds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sorusPosition Context triple: [Thyrsopteridaceae, sorusPosition, abaxial side of fronds]
-
A.
positionSought
Indicates the specific role, job, or position that an entity is aiming to obtain or apply for.
-
B.
opusPosition
Indicates the position or number assigned to a work within a creator’s catalog or opus sequence.
-
C.
subjectPosition
Indicates the spatial or logical position of a subject relative to a reference frame, context, or other entities.
-
D.
SouthernCrossPosition
Indicates the relative location or orientation of something with respect to the Southern Cross constellation.
-
E.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:30 a.m.