Triple
T29019777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holomycota |
E737419
|
entity |
| Predicate | kingdomScope |
P567
|
FINISHED |
| Object | Fungi and close relatives |
—
|
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 and close relatives | Statement: [Holomycota, kingdomScope, Fungi and close relatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: kingdomScope Context triple: [Holomycota, kingdomScope, Fungi and close relatives]
-
A.
kingdom
chosen
Indicates that an entity is classified within a particular biological kingdom in a taxonomic hierarchy.
-
B.
mentionsKingdom
Indicates that one entity explicitly refers to or brings up the topic of a kingdom in relation to another entity.
-
C.
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.
-
D.
clientKingdomOf
Indicates a relationship where one kingdom is politically subordinate or tributary to another, more powerful kingdom while retaining limited internal autonomy.
-
E.
realmRuled
Indicates that one entity serves as the sovereign or governing ruler over a particular realm, territory, or domain.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66004da14819098b0fa2906521298 |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:48 a.m.