Triple
T22863236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morchella americana |
E566979
|
entity |
| Predicate | capAttachment |
P93025
|
FINISHED |
| Object | cap attached to stipe at base |
—
|
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: cap attached to stipe at base | Statement: [Morchella americana, capAttachment, cap attached to stipe at base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capAttachment Context triple: [Morchella americana, capAttachment, cap attached to stipe at base]
-
A.
headAttachment
Indicates that one entity is physically or structurally attached to the head or top part of another entity.
-
B.
capTreatment
Indicates a medical or corrective treatment applied to a tooth’s crown (cap), such as placing or modifying a dental cap or crown.
-
C.
supportsAttachmentTo
Indicates that one entity provides a structural or functional basis for another entity to be attached or affixed to it.
-
D.
capSurface
Indicates that one entity serves as the top or end surface (a cap) enclosing or terminating another entity.
-
E.
attachmentType
chosen
Indicates the specific kind or category of attachment that relates one entity to another.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eff1c18819081dc9dfc1816f746 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.