Triple
T27773882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peer Gynt Suite No. 2 |
E699131
|
entity |
| Predicate | associatedWithPlay |
P202249
|
FINISHED |
| Object | Peer Gynt |
—
|
NE NERFINISHED |
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: Peer Gynt | Statement: [Peer Gynt Suite No. 2, associatedWithPlay, Peer Gynt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPlay Context triple: [Peer Gynt Suite No. 2, associatedWithPlay, Peer Gynt]
-
A.
associatedWithPlayers
Indicates a relationship in which one or more players are connected, linked, or otherwise involved with the referenced entity.
-
B.
associatedWithGame
Indicates that there is a relationship or connection between an entity and a particular game.
-
C.
associatedWithMatch
Indicates a relationship where an entity is linked or connected to a particular match or matching event.
-
D.
associatedWithStand
Indicates a relationship where an entity is linked or connected to a particular stand, such as being located at, operating in, or otherwise related to that stand.
-
E.
playsWith
Indicates that one entity engages in play or recreational activity together with another entity.
- F. None of above. chosen
Provenance (4 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_6a0067cde0f08190b2cd93af5f00d519 |
completed | May 10, 2026, 11:11 a.m. |
| PD | Predicate disambiguation | batch_6a0065820c8c8190994734433c64a30a |
completed | May 10, 2026, 11:01 a.m. |
| PDg | Predicate description generation | batch_6a0067cd38bc8190a719e9d1a287cd95 |
completed | May 10, 2026, 11:11 a.m. |
Created at: April 27, 2026, 5:04 p.m.