Triple
T31613180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 2 in C major, "Ocean" |
E806680
|
entity |
| Predicate | isNumberedWork |
P70295
|
FINISHED |
| Object | 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: 2 | Statement: [Symphony No. 2 in C major, "Ocean", isNumberedWork, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberedWork Context triple: [Symphony No. 2 in C major, "Ocean", isNumberedWork, 2]
-
A.
isNumbered
Indicates that an entity has been assigned a specific number or position in an ordered sequence.
-
B.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
-
C.
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).
-
D.
appearsInWorkNumber
Indicates that an entity is featured or occurs within a specific numbered work in a series or collection.
-
E.
workNumbering
chosen
Indicates that a specific numbering or cataloging identifier is assigned to a work within a larger collection or system.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a8a7bb6c819082c576bf21a6efe4 |
completed | May 3, 2026, 1:45 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:37 p.m.