Triple
T29326015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English horn |
E743643
|
entity |
| Predicate | isCommonlyPlayedBy |
P138103
|
FINISHED |
| Object | oboe players |
—
|
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: oboe players | Statement: [English horn, isCommonlyPlayedBy, oboe players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlyPlayedBy Context triple: [English horn, isCommonlyPlayedBy, oboe players]
-
A.
isOftenPlayedFor
Indicates that one entity is frequently performed, used, or presented for the benefit, enjoyment, or experience of another entity.
-
B.
isTypicallyPlayed
Indicates that an activity, game, or sport is commonly engaged in or performed by a particular type of participant or group.
-
C.
isOftenPlayed
Indicates that an entity is frequently engaged with or performed, typically more often than other comparable entities.
-
D.
typicallyPlays
chosen
Indicates that an entity is most commonly or habitually associated with playing a particular role, instrument, position, or type of game.
-
E.
oftenPlayedDuring
Indicates that one thing (such as a song, piece, or media) is frequently played in the context, time, or situation associated with 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 1:26 p.m.