Triple
T2801903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophiostoma piceae |
E53165
|
entity |
| Predicate | substrate |
P16678
|
FINISHED |
| Object | conifer logs |
—
|
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: conifer logs | Statement: [Ophiostoma piceae, substrate, conifer logs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: substrate Context triple: [Ophiostoma piceae, substrate, conifer logs]
-
A.
isSubstrateOf
Indicates that one entity serves as the material or reactant upon which another entity (typically an enzyme or process) acts in a chemical or biochemical reaction.
-
B.
substratePreference
chosen
Indicates a relationship where an entity tends to occur on, grow in, or utilize a particular physical material or medium as its preferred substrate.
-
C.
hasSubstrateInfluenceOn
Indicates that one substrate affects, modifies, or determines the behavior, activity, or properties of another entity or process.
-
D.
foundInSubstrate
Indicates that something exists, occurs, or is located within a particular substrate or underlying medium.
-
E.
substanceType
Indicates the specific kind or category of substance associated with an entity or relation.
- 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_69ab495a90788190941b6917e1eca3a6 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abde2ec2ac8190bd702ad3eafb6aed |
completed | March 7, 2026, 8:13 a.m. |
| PD | Predicate disambiguation | batch_69abdd059f308190853191f6ffe2bc6f |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:58 p.m.