Triple
T4736396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phaethon |
E105135
|
entity |
| Predicate | warningDirectedAt |
P56136
|
FINISHED |
| Object | mortals who aspire to divine powers |
—
|
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: mortals who aspire to divine powers | Statement: [Phaethon, warningDirectedAt, mortals who aspire to divine powers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warningDirectedAt Context triple: [Phaethon, warningDirectedAt, mortals who aspire to divine powers]
-
A.
warningType
Indicates the specific category or classification of a warning associated with an entity or event.
-
B.
warningIssued
Indicates that a formal warning or alert has been communicated from one entity to another regarding a potential or existing risk, problem, or violation.
-
C.
warningRecipient
chosen
Indicates that one entity is the recipient or target audience of a warning issued by another entity.
-
D.
warningCall
Indicates that one entity initiates a call to another specifically to warn them about a danger, risk, or important cautionary information.
-
E.
warnsAbout
Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
- 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_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. |
Created at: March 20, 2026, 1:19 p.m.