Triple
T11977787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orchis mascula |
E285078
|
entity |
| Predicate | leafMarkings |
P102686
|
FINISHED |
| Object | often dark-spotted 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: often dark-spotted leaves | Statement: [Orchis mascula, leafMarkings, often dark-spotted leaves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leafMarkings Context triple: [Orchis mascula, leafMarkings, often dark-spotted leaves]
-
A.
eggMarkings
Indicates that one entity bears or displays specific markings or patterns on its eggs in relation to another entity or context.
-
B.
petalMarkings
Indicates the pattern, color, or distinctive markings present on the petals of a flower in relation to the flower they belong to.
-
C.
originalTailMarkings
Indicates that an entity possesses or is associated with the initial or native markings found on a tail, prior to any changes or modifications.
-
D.
hasBranchCarvings
Indicates that an entity (such as a tree or wooden object) possesses carvings or engravings specifically on its branches.
-
E.
mayHaveMarkings
Indicates that an entity is permitted or able to possess certain markings or distinguishing signs.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
| PDg | Predicate description generation | batch_69d903a8695c8190bfa9d7ca50834f9f |
completed | April 10, 2026, 2:05 p.m. |
Created at: April 8, 2026, 9:46 p.m.