Triple
T22742317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pisorisporiaceae |
E562444
|
entity |
| Predicate | kingdomCommonName |
P567
|
FINISHED |
| Object | 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: fungi | Statement: [Pisorisporiaceae, kingdomCommonName, fungi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingdomCommonName Context triple: [Pisorisporiaceae, kingdomCommonName, fungi]
-
A.
kingdomAssociatedWith
Indicates a relationship where something is connected or related to a particular kingdom, such as belonging to, originating from, or being governed by that kingdom.
-
B.
recognizedAsKingdom
Indicates that an entity is formally acknowledged or classified as a kingdom within a given system or context.
-
C.
zoogeographicKingdom
Indicates the broad zoogeographic realm or kingdom within which an organism’s natural distribution primarily falls.
-
D.
kingdom
chosen
Indicates that an entity is classified within a particular biological kingdom in a taxonomic hierarchy.
-
E.
animalCommonNameFeatured
Indicates that a particular animal’s common (vernacular) name is prominently highlighted or used as the primary displayed name in a given context.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1797400fc8190bec26726f434f787 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:23 p.m.