Triple
T1303334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pindar's odes |
E27816
|
entity |
| Predicate | intendedPerformance |
P9966
|
FINISHED |
| Object | sung by chorus |
—
|
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: sung by chorus | Statement: [Pindar's odes, intendedPerformance, sung by chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedPerformance Context triple: [Pindar's odes, intendedPerformance, sung by chorus]
-
A.
performedWith
chosen
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
B.
performed
Indicates that an entity carried out, executed, or conducted a specific action, task, or activity.
-
C.
designedToEvoke
Indicates that something was intentionally created or arranged in order to elicit a particular reaction, feeling, or response from an audience or observer.
-
D.
intendedFunction
Indicates that something is designed or purposed to perform a particular role, use, or function.
-
E.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of 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_69a496d7d83481908f83085854e51328 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c116d7d881908ee631258f80980e |
completed | March 1, 2026, 10:43 p.m. |
| PD | Predicate disambiguation | batch_69a4bee8544c8190874efd9bae9bccf9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.