Triple
T19940894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King Iobates of Lycia |
E479303
|
entity |
| Predicate | thenAction |
P87912
|
FINISHED |
| Object | gave Bellerophon his daughter in marriage |
—
|
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: gave Bellerophon his daughter in marriage | Statement: [King Iobates of Lycia, thenAction, gave Bellerophon his daughter in marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thenAction Context triple: [King Iobates of Lycia, thenAction, gave Bellerophon his daughter in marriage]
-
A.
subsequentAction
chosen
Indicates that one action occurs after another in time, following it as a later step or consequence.
-
B.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
C.
attemptedAction
Indicates that an entity made an effort to perform a particular action, regardless of whether the action was successfully completed.
-
D.
requiredAction
Indicates that a specific action must be performed or fulfilled as a necessary condition in the given context.
-
E.
fromAct
Indicates that an entity originates from, is produced by, or results from a specified action or event.
- 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_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. |
Created at: April 10, 2026, 1:54 p.m.