Triple
T4736373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaethon |
E105135
|
entity |
| Predicate | attemptedAction |
P58482
|
FINISHED |
| Object | to drive Helios’s chariot across the sky |
—
|
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: to drive Helios’s chariot across the sky | Statement: [Phaethon, attemptedAction, to drive Helios’s chariot across the sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedAction Context triple: [Phaethon, attemptedAction, to drive Helios’s chariot across the sky]
-
A.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
B.
wasTriedAt
Indicates that a legal case or judicial proceeding involving an entity took place at a specific court or location.
-
C.
requiredAction
Indicates that a specific action must be performed or fulfilled as a necessary condition in the given context.
-
D.
escapeAttempt
Indicates an action where an entity tries to get away from confinement, control, or a restricting situation.
-
E.
actsOn
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd64831c58819098758ac1f7839b3a |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd637e19e081909e415544106c7835 |
completed | March 20, 2026, 3:10 p.m. |
Created at: March 20, 2026, 1:19 p.m.