Triple
T23508427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pezizales |
E572349
|
entity |
| Predicate | includesMorphologicalType |
P1250
|
FINISHED |
| Object | cup fungi |
—
|
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: cup fungi | Statement: [Pezizales, includesMorphologicalType, cup fungi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMorphologicalType Context triple: [Pezizales, includesMorphologicalType, cup fungi]
-
A.
hasMorphologicalType
chosen
Indicates that an entity possesses or is classified by a particular morphological type or structural form.
-
B.
morphismType
Indicates the specific kind or category of morphism that characterizes the structural relationship between two mathematical objects.
-
C.
hasUnusualMorphology
Indicates that an entity possesses structural or anatomical features that deviate significantly from what is typical or expected for its kind.
-
D.
hasMorphologicalMix
Indicates that an entity exhibits a combination of different morphological types or structures within a single form or system.
-
E.
hasContactBinaryMorphology
Indicates that an entity exhibits a binary structure in which two components are in direct physical contact or share a common envelope, forming a contact binary configuration.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a902c0788190840d7df1b5450b4d |
completed | April 29, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:07 p.m.