Triple
T16200301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ganymede (mythology) |
E393180
|
entity |
| Predicate | abductionFormOfZeus |
P23389
|
FINISHED |
| Object | eagle |
—
|
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: eagle | Statement: [Ganymede (mythology), abductionFormOfZeus, eagle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abductionFormOfZeus Context triple: [Ganymede (mythology), abductionFormOfZeus, eagle]
-
A.
attemptedAbductionWithPirithous
Indicates an event where an entity participated with Pirithous in an attempt to abduct someone.
-
B.
abductedBy
Indicates that an entity has been forcibly taken or carried away by another entity against their will.
-
C.
abductedFrom
Indicates that an entity was forcibly taken away or kidnapped from a specified location or source.
-
D.
abductionMotif
chosen
Indicates a relationship where an event, narrative, or depiction involves the motif of one entity abducting or forcibly carrying off another.
-
E.
usedAbductions
Indicates that one entity carried out or relied on abductions (kidnappings) as a method or tactic in relation to another entity or context.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e22709b0d88190b40787e0520d02ab |
completed | April 17, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.