Triple
T29099250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haywire |
E735094
|
entity |
| Predicate | hasReviewAspect |
P152789
|
FINISHED |
| Object | praised for action sequences |
—
|
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: praised for action sequences | Statement: [Haywire, hasReviewAspect, praised for action sequences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReviewAspect Context triple: [Haywire, hasReviewAspect, praised for action sequences]
-
A.
hasBeenReviewedIn
Indicates that an entity has been evaluated or critiqued within a specific review, publication, or reviewing context.
-
B.
hasReviewed
Indicates that one entity has examined, evaluated, or provided feedback on another entity (such as a work, product, or performance).
-
C.
reviewedAs
Indicates that one entity has evaluated, critiqued, or assessed another entity in a particular capacity, role, or context.
-
D.
hasRecension
Indicates that one textual version or edition is a revised or alternative form of another text.
-
E.
hasReviewFocus
chosen
Indicates that a review specifically concentrates on or emphasizes a particular aspect, feature, or component of the subject.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: April 28, 2026, 11:11 a.m.