Triple
T29570552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guitar Concerto No. 2 in C major, Op. 160 |
E753293
|
entity |
| Predicate | hasTypeOfWorkNumber |
P81490
|
FINISHED |
| Object | No. 2 |
—
|
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: No. 2 | Statement: [Guitar Concerto No. 2 in C major, Op. 160, hasTypeOfWorkNumber, No. 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfWorkNumber Context triple: [Guitar Concerto No. 2 in C major, Op. 160, hasTypeOfWorkNumber, No. 2]
-
A.
hasWorkNumberType
Indicates that an entity’s work-related phone number is classified as a specific type (e.g., mobile, landline, extension).
-
B.
hasNumberWithinWork
Indicates that a specific number or numeric value is contained, referenced, or used within a particular work (such as a document, publication, or creative piece).
-
C.
hasSignificantWorkType
Indicates that an entity is associated with a primary or notably important type or category of work.
-
D.
appearsInWorkNumber
chosen
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
E.
hasRoleInWorkType
Indicates that an entity holds a specific role or function within a particular type or category of work.
- 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 28, 2026, 5:57 p.m.