Triple
T26382731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laboulbeniomycetes |
E663180
|
entity |
| Predicate | hostEffect |
P39638
|
FINISHED |
| Object | may affect host behavior |
—
|
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: may affect host behavior | Statement: [Laboulbeniomycetes, hostEffect, may affect host behavior]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostEffect Context triple: [Laboulbeniomycetes, hostEffect, may affect host behavior]
-
A.
eventEffect
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
B.
canonicalEffect
Indicates the standard or primary effect that an action, event, or entity is typically understood to produce.
-
C.
sideEffect
chosen
Indicates that one entity is an unintended or secondary effect resulting from the use or occurrence of another entity.
-
D.
hasEffectIn
Indicates that one entity produces, causes, or exerts an effect within a specified context, system, or environment.
-
E.
placeOfEffect
Indicates the location or setting where an action, event, or effect takes place or is realized.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6430a93a48190854ce71df680b2fa |
completed | May 2, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69f641da05b881909f6283c988639c53 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 26, 2026, 11:20 p.m.