Triple
T6006003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Candida albicans |
E133710
|
entity |
| Predicate | reproducesBy |
P3603
|
FINISHED |
| Object | budding |
—
|
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: budding | Statement: [Candida albicans, reproducesBy, budding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reproducesBy Context triple: [Candida albicans, reproducesBy, budding]
-
A.
hasReproduction
Indicates that one entity possesses or exhibits a particular mode, process, or capability of reproduction.
-
B.
repopulatedBy
Indicates that something is populated again or refilled with members or inhabitants by a specified agent or source.
-
C.
reproductionType
chosen
Indicates the mode or method by which an organism reproduces or generates offspring.
-
D.
recoveryBy
Indicates that one entity regains or restores something (such as health, function, or a resource) through the action, intervention, or influence of another entity.
-
E.
reproductionConstraint
Indicates a limitation, condition, or rule that restricts or governs how reproduction or generative processes may occur between entities.
- 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_69c00872444c8190bfaf1739dcec765c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f128354819088971ee398cbda77 |
completed | March 22, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.