Triple
T50267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch elm disease |
E987
|
entity |
| Predicate | hostRange |
P2901
|
FINISHED |
| Object | European elms |
—
|
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: European elms | Statement: [Dutch elm disease, hostRange, European elms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostRange Context triple: [Dutch elm disease, hostRange, European elms]
-
A.
hubFor
Indicates that one entity serves as a central node or focal point through which activities, connections, or resources related to another entity are organized or routed.
-
B.
hostsExperiment
Indicates that one entity provides the environment or infrastructure in which another entity’s experiment is conducted or run.
-
C.
postalCodeRange
Indicates that one entity specifies a contiguous range of postal codes applicable to another entity or context.
-
D.
hostsEvent
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
E.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
- F. None of above. chosen
Provenance (4 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24ba7016481909d595402712db6e2 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac23f04819080cef9365ed990d4 |
completed | Feb. 28, 2026, 1:54 a.m. |
| PDg | Predicate description generation | batch_69a24ba5da048190a484963cb5a9bb2b |
completed | Feb. 28, 2026, 1:57 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.