Triple
T38389123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Miraculous Mandarin |
E899659
|
entity |
| Predicate | orchestralSuiteYear |
P190829
|
FINISHED |
| Object | 1927 |
—
|
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: 1927 | Statement: [The Miraculous Mandarin, orchestralSuiteYear, 1927]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orchestralSuiteYear Context triple: [The Miraculous Mandarin, orchestralSuiteYear, 1927]
-
A.
orchestralCatalogNumber
Indicates the catalog or identifying number assigned to a musical work within a composer's orchestral catalog or a specific orchestral cataloging system.
-
B.
hasOrchestralSuite
Indicates that a musical work is associated with, or has been arranged into, an orchestral suite derived from it.
-
C.
orchestrationDate
Indicates the date on which the orchestration (coordination or arrangement of related actions or processes) occurs or is scheduled to occur.
-
D.
orchestralVersionCompleted
Indicates that an orchestral arrangement of a work has been fully created and finalized.
-
E.
orchestralArrangement
Indicates that one musical work is arranged or adapted specifically for performance by an orchestra.
- F. None of above. chosen
Provenance (4 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fcd148e6d4819082c118832ecc599b |
completed | May 7, 2026, 5:52 p.m. |
Created at: May 3, 2026, 4:31 p.m.