Triple
T10974648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hero |
E259335
|
entity |
| Predicate | reportedAs |
P96391
|
FINISHED |
| Object | dead |
—
|
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: dead | Statement: [Hero, reportedAs, dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reportedAs Context triple: [Hero, reportedAs, dead]
-
A.
reportedOn
Indicates that one entity has provided an account, description, or coverage of another entity, typically as news, documentation, or an official report.
-
B.
resultsReportedAs
Indicates that the outcomes or findings of an activity, process, or evaluation are communicated or documented in a specified form, format, or medium.
-
C.
reportsCaseTo
Indicates that one party formally submits or communicates a case, incident, or issue to another party, typically an authority or responsible entity.
-
D.
reportsImplementedBy
Indicates that a report is realized, produced, or carried out by a specific implementing entity or system.
-
E.
reportsAlsoKnownAs
Indicates that an entity is known or referred to by an alternative report name or alias.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771f3794c8190b1992b4695139b62 |
completed | April 9, 2026, 9:31 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69d732242fdc8190be77d1f730a42935 |
completed | April 9, 2026, 4:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.