Triple
T20303851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigel Hess |
E505553
|
entity |
| Predicate | hasParticularlyWorkedOn |
P45535
|
FINISHED |
| Object | BBC dramas |
—
|
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: BBC dramas | Statement: [Nigel Hess, hasParticularlyWorkedOn, BBC dramas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParticularlyWorkedOn Context triple: [Nigel Hess, hasParticularlyWorkedOn, BBC dramas]
-
A.
hasWorkedIn
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
B.
hasWorkDedicatedTo
Indicates that one entity has a work (such as a book, artwork, or composition) that is formally dedicated to another entity.
-
C.
workTypeContributedTo
chosen
Indicates that an entity contributed to the creation, development, or production of a particular type of work.
-
D.
includedWorkOn
Indicates that one entity contains, features, or incorporates another entity as a work or component within it.
-
E.
workedUnder
Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority of 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6773e0864819095d272659cd2074d |
completed | April 20, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:17 a.m.