Triple
T31116603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D 944 |
E793105
|
entity |
| Predicate | alternativeWorkNumber |
P81991
|
FINISHED |
| Object | Symphony No. 8 |
—
|
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: Symphony No. 8 | Statement: [D 944, alternativeWorkNumber, Symphony No. 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeWorkNumber Context triple: [D 944, alternativeWorkNumber, Symphony No. 8]
-
A.
alternateNumber
Indicates that one entity serves as an alternative or secondary number (such as a phone or contact number) for another entity.
-
B.
associatedNumber
Indicates a relationship where a specific number is linked or assigned to an entity as its associated value.
-
C.
worksAsContactFor
Indicates that one entity serves as the designated contact person or liaison for another entity.
-
D.
worksNumber
chosen
Indicates that an entity is identified or referenced by a specific works number, typically denoting a particular work, item, or production instance.
-
E.
officeNumber
Indicates the specific room or suite number assigned to an office within a building or complex.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 29, 2026, 9:04 p.m.