Triple
T934367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eumaeus |
E20161
|
entity |
| Predicate | helpsWith |
P16415
|
FINISHED |
| Object | Odysseus’ return to power in Ithaca |
—
|
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: Odysseus’ return to power in Ithaca | Statement: [Eumaeus, helpsWith, Odysseus’ return to power in Ithaca]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpsWith Context triple: [Eumaeus, helpsWith, Odysseus’ return to power in Ithaca]
-
A.
hasHelpPoint
Indicates that one entity provides or contains a designated help or assistance point for another entity.
-
B.
helpedForm
Indicates that one entity contributed significantly to the creation, establishment, or founding of another entity.
-
C.
providesSupportTo
chosen
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
D.
typeOfSupport
Indicates the kind or category of assistance, help, or backing provided in a given context.
-
E.
supportBase
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
- 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3bcad2481908b83575b2fb80d14 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b299c4d881908a57ac2711676cd7 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.