Triple
T38438839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Piece of Work |
E906429
|
entity |
| Predicate | hasReviewGenre |
P191103
|
FINISHED |
| Object | critical documentary |
—
|
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: critical documentary | Statement: [A Piece of Work, hasReviewGenre, critical documentary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReviewGenre Context triple: [A Piece of Work, hasReviewGenre, critical documentary]
-
A.
hasGivenGenre
Indicates that an entity is associated with a specific genre that has been assigned or designated to it.
-
B.
hasRecension
Indicates that one textual version or edition is a revised or alternative form of another text.
-
C.
hasUseGenre
Indicates that something (such as a work, product, or item) is associated with or categorized under a particular genre for its use or purpose.
-
D.
hasReviewed
Indicates that one entity has examined, evaluated, or provided feedback on another entity (such as a work, product, or performance).
-
E.
hasGenreAsPerception
chosen
Indicates that something is associated with a genre specifically in terms of how it is perceived or interpreted, rather than as an objective classification.
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:31 p.m.