Triple
T1000738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antinous |
E21595
|
entity |
| Predicate | leadsGroup |
P3717
|
FINISHED |
| Object | the suitors feasting in Odysseus’s palace |
—
|
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: the suitors feasting in Odysseus’s palace | Statement: [Antinous, leadsGroup, the suitors feasting in Odysseus’s palace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadsGroup Context triple: [Antinous, leadsGroup, the suitors feasting in Odysseus’s palace]
-
A.
leadingOrgan
Indicates that one entity serves as the primary or most responsible organizing body or authority for another entity or activity.
-
B.
leadSingle
Indicates that an entity serves as the primary or featured performer, contributor, or focus in a single work or instance.
-
C.
leads
chosen
Indicates having primary responsibility for directing, guiding, or managing another entity or group toward a goal or outcome.
-
D.
leadSingleFrom
Indicates that one entity serves as the lead single taken from another entity, typically a larger work such as an album or release.
-
E.
labelGroup
Indicates that an entity is assigned to or associated with a particular group label used for categorization or organization.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4fb18b88190ae2d620aaaff4f90 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.