Triple
T2350991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 28 Weeks Later (cameo)? |
E47446
|
entity |
| Predicate | allegedCreditStatus |
P16813
|
FINISHED |
| Object | uncredited |
—
|
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: uncredited | Statement: [28 Weeks Later (cameo)?, allegedCreditStatus, uncredited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedCreditStatus Context triple: [28 Weeks Later (cameo)?, allegedCreditStatus, uncredited]
-
A.
allegedStatus
chosen
Indicates that a particular status or condition is claimed or asserted about an entity, but has not been confirmed as true.
-
B.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
-
C.
hasBureau
Indicates that an entity is associated with or possesses a specific bureau, such as an office, department, or administrative unit.
-
D.
hasDisputedStatus
Indicates that the status or classification of something is contested, uncertain, or not universally agreed upon.
-
E.
hasDisputedStatusWith
Indicates that there is a contested or unresolved status, claim, or standing between the related entities.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abcb802da08190980100444010f91e |
completed | March 7, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69abc5981ce48190a3f7852d28276e11 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:54 p.m.