Triple
T23568654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IV. The Explorers |
E580038
|
entity |
| Predicate | workCatalogueWithWork |
P88855
|
FINISHED |
| Object | Symphony No. 1 |
—
|
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. 1 | Statement: [IV. The Explorers, workCatalogueWithWork, Symphony No. 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workCatalogueWithWork Context triple: [IV. The Explorers, workCatalogueWithWork, Symphony No. 1]
-
A.
workCatalogueNumberOfWork
Indicates the catalogue number assigned to a specific work within a cataloging or classification system.
-
B.
workCatalogueScope
chosen
Indicates that a work is included within the defined scope or coverage of a particular catalogue.
-
C.
workRepresented
Indicates that one entity is a representation (such as a depiction, adaptation, or portrayal) of another work.
-
D.
hasCatalogedWorkOn
Indicates that an entity has formally recorded, listed, or documented another entity as a work within a catalog or collection.
-
E.
worksFrom
Indicates that an entity performs its work or duties starting from or based at a specified location or source.
- 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_69e24601a9108190bc31e83833c980e4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1afd15ca48190afd119ec1b4a07b2 |
completed | April 29, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69f118bcc0b08190b25a8dddfd461a0e |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:35 p.m.