Triple
T25728071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four on Six |
E645162
|
entity |
| Predicate | commonlyStudiedBy |
P1945
|
FINISHED |
| Object | jazz guitar students |
—
|
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: jazz guitar students | Statement: [Four on Six, commonlyStudiedBy, jazz guitar students]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyStudiedBy Context triple: [Four on Six, commonlyStudiedBy, jazz guitar students]
-
A.
widelyStudiedIn
Indicates that something has been extensively researched, analyzed, or examined within a particular field, domain, or context.
-
B.
studiedBy
chosen
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
-
C.
alsoStudied
Indicates that an entity pursued additional studies in another subject, field, or institution besides a primary one.
-
D.
oftenStudiedBetween
Indicates that something is frequently examined, researched, or analyzed in relation to two or more entities.
-
E.
oftenStudiedWith
Indicates that two subjects or topics are frequently studied together, typically within the same context, course, or learning activity.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 11:08 p.m.