Triple
T37456750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infestor |
E930818
|
entity |
| Predicate | abilityType_FungalGrowth |
P187856
|
FINISHED |
| Object | area-of-effect crowd control |
—
|
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: area-of-effect crowd control | Statement: [Infestor, abilityType_FungalGrowth, area-of-effect crowd control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abilityType_FungalGrowth Context triple: [Infestor, abilityType_FungalGrowth, area-of-effect crowd control]
-
A.
notFungi
Indicates that the subject is explicitly classified as not belonging to the category of fungi.
-
B.
fruitingBodyType
Indicates the type or form of the fruiting body produced by an organism (e.g., mushroom, puffball, bracket).
-
C.
usesBotrytisCinerea
Indicates that an entity employs or applies the fungus *Botrytis cinerea* (e.g., as a tool, agent, or method) in carrying out some process or activity.
-
D.
signOfInfestation
Indicates that one entity serves as evidence or indication that another entity is infested or experiencing an infestation.
-
E.
typicalFungiComponent
Indicates that something is a characteristic or commonly occurring component or part of fungi.
- F. None of above. chosen
Provenance (4 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69fb92ee27408190b0116ef2d789abac |
completed | May 6, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.