Triple
T20246914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryoria lichens |
E498446
|
entity |
| Predicate | thallusMorphology |
P139384
|
FINISHED |
| Object | hair-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: hair-like | Statement: [Bryoria lichens, thallusMorphology, hair-like]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thallusMorphology Context triple: [Bryoria lichens, thallusMorphology, hair-like]
-
A.
chloroplastMorphology
Indicates the structural form, shape, and organization of chloroplasts in a cell.
-
B.
hasSporophyteMorphology
Indicates that an entity exhibits the structural form or physical characteristics typical of a sporophyte stage in its life cycle.
-
C.
gametophyteType
Indicates the specific kind or form of gametophyte (the haploid, gamete-producing life stage) associated with an organism or taxon.
-
D.
fruitingBodyTexture
Indicates the type or quality of texture exhibited by an organism’s fruiting body in the context of its reproductive structure.
-
E.
fruitingBodyType
Indicates the type or form of the fruiting body produced by an organism (e.g., mushroom, puffball, bracket).
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a3c61481909413e042d76cc580 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:40 p.m.