Triple
T31079848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lichas |
E792068
|
entity |
| Predicate | bringsObjectFrom |
P171131
|
FINISHED |
| Object | Heracles |
—
|
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: Heracles | Statement: [Lichas, bringsObjectFrom, Heracles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bringsObjectFrom Context triple: [Lichas, bringsObjectFrom, Heracles]
-
A.
broughtToWorldFrom
Indicates that an entity was transported or introduced into a particular world or realm from another origin location or world.
-
B.
broughtTo
Indicates that one entity caused another entity or object to be transported or accompanied to a particular destination or recipient.
-
C.
broughtOn
Indicates that one entity caused, initiated, or was responsible for the occurrence or introduction of another entity or event.
-
D.
broughtBack
Indicates that an entity caused another entity to return to a previous place, state, or condition.
-
E.
givesObjectToOdysseus
Indicates that one entity transfers or presents an object to Odysseus.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f698ad83a08190a6834056ccc3e3a4 |
completed | May 3, 2026, 12:37 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f697e92e2c8190bed50d5ba0981b64 |
completed | May 3, 2026, 12:33 a.m. |
Created at: April 29, 2026, 9:02 p.m.