Triple
T14458424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOT investigative programme |
E358514
|
entity |
| Predicate | journalisticStyle |
P89241
|
FINISHED |
| Object | in-depth reporting |
—
|
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: in-depth reporting | Statement: [MOT investigative programme, journalisticStyle, in-depth reporting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journalisticStyle Context triple: [MOT investigative programme, journalisticStyle, in-depth reporting]
-
A.
journalismType
chosen
Indicates the specific category or style of journalism that characterizes a given journalistic work or activity.
-
B.
narrativeStyle
Indicates how a narrative is told, such as the point of view, tone, and structural approach used to present a story or account.
-
C.
investigativeStyle
Indicates the manner or approach an entity uses when conducting investigations or inquiries.
-
D.
reporterStyle
Indicates that one entity presents information in the manner or stylistic approach characteristic of a reporter or journalistic reporting.
-
E.
rhetoricalStyle
Indicates the characteristic manner or technique of expression used in communication, such as tone, structure, and persuasive strategies.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91aabebc819097eb61b2d81c9a91 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.