Triple
T30935587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matt Fraction |
E788113
|
entity |
| Predicate | adaptationInvolvedIn |
P174096
|
FINISHED |
| Object | Hawkeye (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: Hawkeye (TV series) | Statement: [Matt Fraction, adaptationInvolvedIn, Hawkeye (TV series)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adaptationInvolvedIn Context triple: [Matt Fraction, adaptationInvolvedIn, Hawkeye (TV series)]
-
A.
adaptationIn
Indicates that something appears, is represented, or takes place within a particular adaptation of an original work.
-
B.
adaptation
Indicates a relationship where one entity changes or is modified to better suit, function within, or correspond to another entity or context.
-
C.
adaptationBy
Indicates a relationship where one entity has been modified, transformed, or reworked by another entity into a new form or version.
-
D.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
E.
hasHumanAdaptation
Indicates that something has been modified, designed, or adjusted specifically to suit human use, abilities, or needs.
- F. None of above. chosen
Provenance (4 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: April 29, 2026, 8:52 p.m.