Triple
T54215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet of Things |
E1067
|
entity |
| Predicate | enablesApplication |
P2186
|
FINISHED |
| Object | predictive maintenance |
—
|
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: predictive maintenance | Statement: [Internet of Things, enablesApplication, predictive maintenance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesApplication Context triple: [Internet of Things, enablesApplication, predictive maintenance]
-
A.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
B.
appliesTo
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
C.
supportsActivity
chosen
Indicates that one entity provides the necessary conditions, resources, or environment for another entity’s activity to occur or be sustained.
-
D.
appliesAcross
Indicates that a condition, rule, or property holds uniformly over multiple items, cases, or contexts.
-
E.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b3a9e848190b80de3c858678b3a |
completed | Feb. 28, 2026, 1:56 a.m. |
| PD | Predicate disambiguation | batch_69a24ac52fb08190aa7c38f83434f795 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.