Triple
T36046190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pegasus |
E1042675
|
entity |
| Predicate | helpedHero |
P49758
|
FINISHED |
| Object | Bellerophon defeat the Chimera |
—
|
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: Bellerophon defeat the Chimera | Statement: [Pegasus, helpedHero, Bellerophon defeat the Chimera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpedHero Context triple: [Pegasus, helpedHero, Bellerophon defeat the Chimera]
-
A.
helpsProtagonistWith
chosen
Indicates that one entity assists the protagonist in performing, achieving, or dealing with something specified by the other entity.
-
B.
helpsIn
Indicates that one entity provides assistance, support, or aid to another entity in performing or achieving a particular task, activity, or goal.
-
C.
helpedCause
Indicates that one entity contributed to bringing about, enabling, or facilitating an outcome or event involving another entity.
-
D.
laterHelps
Indicates that one entity provides help or assistance to another at a subsequent time rather than immediately.
-
E.
heroicAction
Indicates that an entity performs a brave, selfless, or morally admirable action, often involving risk or sacrifice for the benefit of others.
- 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_69f76e2e41f8819091f9fb0536920fec |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.