Triple
T36303930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawkeye (2012) |
E893893
|
entity |
| Predicate | awardWinningIssue |
P195475
|
FINISHED |
| Object | Hawkeye (2012) #11 |
—
|
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 (2012) #11 | Statement: [Hawkeye (2012), awardWinningIssue, Hawkeye (2012) #11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: awardWinningIssue Context triple: [Hawkeye (2012), awardWinningIssue, Hawkeye (2012) #11]
-
A.
awardWith
Indicates that one entity grants or presents an award, prize, or honor to another entity.
-
B.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
C.
awardConferred
Indicates that an award or honor has been formally granted by one entity to another.
-
D.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
-
E.
awardFocus
Indicates that an award or honor is specifically directed toward, centered on, or primarily concerned with a particular entity.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
| PDg | Predicate description generation | batch_69fdd2bda90881909aa229194d014ba7 |
completed | May 8, 2026, 12:10 p.m. |
Created at: May 3, 2026, 4:09 p.m.