Triple
T19940886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Iobates of Lycia |
E479303
|
entity |
| Predicate | questAssigned |
P137927
|
FINISHED |
| Object | slay 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: slay the Chimera | Statement: [King Iobates of Lycia, questAssigned, slay the Chimera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: questAssigned Context triple: [King Iobates of Lycia, questAssigned, slay the Chimera]
-
A.
commandedMission
Indicates that one entity served as the commanding leader or officer in charge of a particular mission carried out by another entity.
-
B.
publicMission
Indicates that an entity carries out a mission or activity intended for the general public or serving public interests.
-
C.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
D.
missionOrder
Indicates that one mission is ordered, sequenced, or prioritized relative to another within an overall mission plan.
-
E.
questType
Indicates the specific category or nature of a quest that characterizes what kind of mission or objective it represents.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a1a8df4819094e84855465df6c0 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f47c508190853c4e009c6b5566 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.