Triple
T37450093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haemophilus |
E930650
|
entity |
| Predicate | requiresGrowthFactor |
P40898
|
FINISHED |
| Object | X factor (hemin) |
—
|
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: X factor (hemin) | Statement: [Haemophilus, requiresGrowthFactor, X factor (hemin)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresGrowthFactor Context triple: [Haemophilus, requiresGrowthFactor, X factor (hemin)]
-
A.
growthFactor
Indicates a relationship where one entity promotes, regulates, or contributes to the increase, development, or expansion of another entity.
-
B.
growthRequirement
chosen
Indicates that one entity specifies the necessary conditions or factors required for the growth or development of another entity.
-
C.
isFastGrowing
Indicates that an entity increases in size, quantity, or impact at a rapid or above-average rate over time.
-
D.
hasVolumeGrowth
Indicates that an entity’s volume has increased over time or relative to a previous state or reference.
-
E.
hasGrowthRate
Indicates the rate at which something increases in size, quantity, or value over a given period of time.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0049e40d60819081e3899d8d9fca51 |
completed | May 10, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_6a0048c47b548190ad31b2901cc3784a |
completed | May 10, 2026, 8:58 a.m. |
Created at: May 3, 2026, 4:17 p.m.