Triple
T31139926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chorus of Troezenian women |
E793751
|
entity |
| Predicate | audienceRelation |
P62009
|
FINISHED |
| Object | stand-in for the civic community |
—
|
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: stand-in for the civic community | Statement: [Chorus of Troezenian women, audienceRelation, stand-in for the civic community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceRelation Context triple: [Chorus of Troezenian women, audienceRelation, stand-in for the civic community]
-
A.
relationshipToAudience
Indicates the nature or type of connection an entity has with a specified audience, such as role, stance, or relevance.
-
B.
relatesToAudience
chosen
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
C.
audienceRole
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
-
D.
relationshipToSpeaker
Indicates that one entity stands in a specific familial, social, or interpersonal relation to the speaker.
-
E.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:05 p.m.