Triple
T5631815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhynia |
E147849
|
entity |
| Predicate | lackedStructure |
P13714
|
FINISHED |
| Object | true leaves |
—
|
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: true leaves | Statement: [Rhynia, lackedStructure, true leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lackedStructure Context triple: [Rhynia, lackedStructure, true leaves]
-
A.
skeletonLacks
Indicates that an entity’s skeleton does not possess or is missing a specified bone, feature, or structural component.
-
B.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
C.
typicallyLack
chosen
Indicates that one entity is characteristically or usually without, or does not possess, another entity or attribute.
-
D.
affectedStructure
Indicates that one entity is the structure, component, or part that is impacted, altered, or influenced by another entity or event.
-
E.
hasHumanStructure
Indicates that one entity possesses or exhibits a structural form or organization characteristic of humans.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225e8e848190a9ccd48fc0d74e5c |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.