Triple
T7105276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaeans |
E165565
|
entity |
| Predicate | goalInTrojanWar |
P74927
|
FINISHED |
| Object | to recover Helen of Sparta |
—
|
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 recover Helen of Sparta | Statement: [Achaeans, goalInTrojanWar, to recover Helen of Sparta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalInTrojanWar Context triple: [Achaeans, goalInTrojanWar, to recover Helen of Sparta]
-
A.
goalOfAeneas
Indicates that the specified entity represents a goal, aim, or objective pursued by Aeneas.
-
B.
HeraBribe
Indicates that Hera offers something of value as a bribe to influence or persuade another entity to act in her favor.
-
C.
AphroditeBribe
Indicates that one entity (Aphrodite) offers or gives a persuasive incentive or reward to another entity in order to influence their decision or allegiance.
-
D.
AthenaBribe
Indicates that one entity offers or gives something of value to another as a bribe, specifically involving or attributed to Athena.
-
E.
sideTakenInTitanomachy
Indicates which faction or side an entity aligned with or supported during the Titanomachy conflict.
- 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5b892008190827fa1e5eab2e558 |
completed | March 27, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c313e481908b61a23fc89f9332 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a15b088190bee9a23e94aaac53 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:42 p.m.