Triple
T2647193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophiostoma quercus |
E53811
|
entity |
| Predicate | associatedWithHost |
P38981
|
FINISHED |
| Object | oak trees |
—
|
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: oak trees | Statement: [Ophiostoma quercus, associatedWithHost, oak trees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithHost Context triple: [Ophiostoma quercus, associatedWithHost, oak trees]
-
A.
hostAssociation
chosen
Indicates a relationship in which one entity serves as the host or primary supporting environment for another entity.
-
B.
alsoHosted
Indicates that the subject entity, in addition to others, served as a host for the same event or activity.
-
C.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
D.
associatedWithCluster
Indicates that an entity is linked or grouped with a particular cluster, typically sharing common characteristics or membership within that cluster.
-
E.
associatedSystem
Indicates that one entity is functionally or contextually linked to a particular system with which it interacts or to which it belongs.
- 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_69ab495e192081909c77b622e8e7e15a |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd919bf2c81908feb768f3391e985 |
completed | March 7, 2026, 7:51 a.m. |
| PD | Predicate disambiguation | batch_69abd814298c8190952f05aed43f6bb8 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:53 p.m.