Triple
T23280541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proetus |
E588847
|
entity |
| Predicate | sentHeroOnQuest |
P27507
|
FINISHED |
| Object | Bellerophon |
—
|
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: Bellerophon | Statement: [Proetus, sentHeroOnQuest, Bellerophon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sentHeroOnQuest Context triple: [Proetus, sentHeroOnQuest, Bellerophon]
-
A.
sentMissionTo
Indicates that one entity dispatched or assigned another entity to carry out a specific mission at a particular destination or context.
-
B.
sentOnMissionBy
chosen
Indicates that one entity was assigned or dispatched on a mission by another entity.
-
C.
questAssigned
Indicates that a quest has been given by one entity to another, establishing an assignment relationship between them.
-
D.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
-
E.
hadMission
Indicates that an entity (such as a person, organization, or vehicle) was assigned or carried out a specific mission or operation.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19642b46481909fd455acd2155792 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:55 p.m.