Triple
T4311048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judgment of Paris |
E94074
|
entity |
| Predicate | AthenaBribe |
P56386
|
FINISHED |
| Object | promise of military glory |
—
|
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: promise of military glory | Statement: [Judgment of Paris, AthenaBribe, promise of military glory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AthenaBribe Context triple: [Judgment of Paris, AthenaBribe, promise of military glory]
-
A.
ArtemisIs
Indicates that something or someone is identified as, or has the status/role of, Artemis.
-
B.
sideTakenInTitanomachy
Indicates which faction or side an entity aligned with or supported during the Titanomachy conflict.
-
C.
ApolloDomain
Indicates a relationship where something belongs to, is governed by, or falls under the scope of the Apollo domain or authority.
-
D.
eraOfMyth
Indicates a temporal relationship where an event, story, or phenomenon belongs to or takes place during a mythological or legendary era.
-
E.
patronDeityOf
Indicates that one entity serves as the protective or primary deity associated with, worshipped by, or presiding over another entity (such as a person, group, or place).
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350d6cba08190a9440cee7b9dc40d |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:11 p.m.