Triple
T15593795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curtis Amy |
E374815
|
entity |
| Predicate | alsoPlayed |
P119357
|
FINISHED |
| Object | soprano saxophone |
—
|
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: soprano saxophone | Statement: [Curtis Amy, alsoPlayed, soprano saxophone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoPlayed Context triple: [Curtis Amy, alsoPlayed, soprano saxophone]
-
A.
alsoPlayedIn
Indicates that an entity (such as a person or performer) participated or appeared in another work, production, or context in addition to the one already referenced.
-
B.
playedWith
Indicates that one entity engaged in play or a playful activity together with another entity.
-
C.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
D.
playedKeyRoleIn
Indicates that an entity had a major, influential, or decisive impact on the occurrence, outcome, or success of another entity or event.
-
E.
laterPlayedFor
Indicates that an individual was a member of or played for a team or organization at a time after a previously referenced team or organization.
- 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_69d85cce25008190b13b52745fbd719b |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e5e43d48190a8fd367f13f1c7e1 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:12 a.m.