Triple
T21133395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pantomime (Daphnis et Chloé) |
E520745
|
entity |
| Predicate | alsoPerformedAs |
P119357
|
FINISHED |
| Object | standalone concert piece |
—
|
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: standalone concert piece | Statement: [Pantomime (Daphnis et Chloé), alsoPerformedAs, standalone concert piece]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoPerformedAs Context triple: [Pantomime (Daphnis et Chloé), alsoPerformedAs, standalone concert piece]
-
A.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
B.
alsoPlayed
chosen
Indicates that the same entity participated in or performed in an additional role, work, or context beyond the one already specified.
-
C.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
D.
alsoServedAs
Indicates that an entity held an additional role or position beyond the primary one already mentioned.
-
E.
laterPerformedBy
Indicates that an action or event is carried out by a particular agent at a later time than another referenced action or event.
- 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_69e0b50b53048190ae34e8abbe3c5ada |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235847948190984c7009ca7f6189 |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:56 p.m.