Triple
T33921857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luther universe |
E869636
|
entity |
| Predicate | centeredOnWork |
P16614
|
FINISHED |
| Object | Luther (TV series) |
—
|
NE NERFINISHED |
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: Luther (TV series) | Statement: [Luther universe, centeredOnWork, Luther (TV series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centeredOnWork Context triple: [Luther universe, centeredOnWork, Luther (TV series)]
-
A.
focusesOnWork
Indicates that an entity directs its attention, effort, or primary activity toward work-related tasks or responsibilities.
-
B.
developmentCenteredOn
Indicates that the primary focus or core activity of a development process, project, or initiative is oriented around a particular entity or aspect.
-
C.
centralWork
chosen
Indicates that a particular work is the primary, most important, or focal work associated with an entity or context.
-
D.
placeInWork
Indicates that one entity is located or occurs within the spatial or structural context of another entity in a work.
-
E.
workWithin
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined 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_69f349992c508190aa4afa24a086cc8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.