Triple
T6216866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sordariales |
E139008
|
entity |
| Predicate | ascocarpType |
P67328
|
FINISHED |
| Object | perithecial ascocarp |
—
|
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: perithecial ascocarp | Statement: [Sordariales, ascocarpType, perithecial ascocarp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ascocarpType Context triple: [Sordariales, ascocarpType, perithecial ascocarp]
-
A.
sporangiaType
Indicates the type or form of sporangia associated with an organism or structure.
-
B.
fruitEnclosure
Indicates a relationship where an enclosure, container, or structure is specifically used to hold, protect, or surround fruit.
-
C.
fruitingBodyType
chosen
Indicates the type or form of the fruiting body produced by an organism (e.g., mushroom, puffball, bracket).
-
D.
hymeniumType
Indicates the type or structure of the spore-bearing surface (hymenium) in a fungus, describing how and where its reproductive cells are arranged.
-
E.
sporeType
Indicates the specific kind or category of spores associated with an entity.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062a1eb3881908c7f735cf9c429ce |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.