Triple
T27773893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peer Gynt Suite No. 2 |
E699131
|
entity |
| Predicate | isArrangedFrom |
P46740
|
FINISHED |
| Object | stage incidental music |
—
|
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: stage incidental music | Statement: [Peer Gynt Suite No. 2, isArrangedFrom, stage incidental music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isArrangedFrom Context triple: [Peer Gynt Suite No. 2, isArrangedFrom, stage incidental music]
-
A.
isArrangementOf
chosen
Indicates that one entity is a specific ordering or configuration of the components or elements of another entity.
-
B.
arranges
Indicates that one entity organizes, coordinates, or puts in order some event, objects, or circumstances involving another entity.
-
C.
commonlyArrangedFor
Indicates that one entity is typically organized, scheduled, or set up on behalf of another entity.
-
D.
canBeArrangedFor
Indicates that one entity is able to be scheduled, organized, or set up on behalf of or for the benefit of another entity.
-
E.
arrangement
Indicates a relationship where entities are organized, ordered, or positioned in a particular configuration or sequence relative to one another.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63798a67c8190876c47dacf89af6e |
completed | May 2, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:04 p.m.