Triple
T1207039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Manufacturing UK |
E25911
|
entity |
| Predicate | implementsProgram |
P24641
|
FINISHED |
| Object | apprenticeship schemes |
—
|
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: apprenticeship schemes | Statement: [Toyota Manufacturing UK, implementsProgram, apprenticeship schemes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: implementsProgram Context triple: [Toyota Manufacturing UK, implementsProgram, apprenticeship schemes]
-
A.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
B.
componentProgram
Indicates that one entity is a component or module that forms part of a larger program or software system represented by the other entity.
-
C.
programOn
Indicates that a program is scheduled to be broadcast or presented on a particular channel, station, platform, or device.
-
D.
createdProgram
Indicates that an entity authored, developed, or produced a particular program (such as software or a coded application).
-
E.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
- 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdc483b481908e5bfef5d2f4fc5a |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:46 p.m.