Triple
T36766699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iliad, Book 17 |
E908358
|
entity |
| Predicate | divineIntervention |
P168509
|
FINISHED |
| Object | Apollo aids the Trojans |
—
|
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: Apollo aids the Trojans | Statement: [Iliad, Book 17, divineIntervention, Apollo aids the Trojans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divineIntervention Context triple: [Iliad, Book 17, divineIntervention, Apollo aids the Trojans]
-
A.
divineInteraction
chosen
Indicates an interaction or exchange occurring between a divine being (or force) and another entity.
-
B.
divineProtection
Indicates a relationship where one entity safeguards, blesses, or shields another through supernatural or sacred power.
-
C.
divineAgent
Indicates that the related entity acts as a deity or supernatural agent responsible for causing or overseeing the associated event or state.
-
D.
miraclePerformedBy
Indicates that a miraculous event is carried out or caused by a particular agent or entity.
-
E.
divineStatus
Indicates that an entity possesses a sacred, godlike, or religiously exalted status in relation to another entity or within a given belief system.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.