Triple
T10556251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macmillan Learning |
E249092
|
entity |
| Predicate | usesTechnologyFor |
P41801
|
FINISHED |
| Object | digital course delivery |
—
|
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: digital course delivery | Statement: [Macmillan Learning, usesTechnologyFor, digital course delivery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTechnologyFor Context triple: [Macmillan Learning, usesTechnologyFor, digital course delivery]
-
A.
technologyUse
chosen
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
B.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
C.
technologyUsedBy
Indicates that a particular technology is employed or utilized by a specified entity.
-
D.
associatedWithTechnology
Indicates a relationship where an entity is connected to, involved with, or utilizes a particular technology.
-
E.
usesSearchTechnologyFrom
Indicates that one entity employs or relies on the search technology developed or provided by another entity.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52713eaa48190936b4b15e2c7e827 |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:35 p.m.