Triple
T31070045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoboken catalogue |
E791790
|
entity |
| Predicate | mainCategoryFor |
P64612
|
FINISHED |
| Object | symphonies (Hob. I) |
—
|
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: symphonies (Hob. I) | Statement: [Hoboken catalogue, mainCategoryFor, symphonies (Hob. I)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCategoryFor Context triple: [Hoboken catalogue, mainCategoryFor, symphonies (Hob. I)]
-
A.
canonicalCategory
Indicates that an entity is assigned to its primary or standard category within a classification system.
-
B.
macroCategory
Indicates that one category functions as a broader, higher-level grouping that encompasses another more specific category.
-
C.
mainImportCategory
Indicates the primary category under which an entity’s imported items or resources are classified.
-
D.
mainSeriesCategory
Indicates that one series is the primary or overarching category under which another series is grouped or classified.
-
E.
coreCategory
chosen
Indicates that one entity is the primary or fundamental category to which another entity belongs or is classified under.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 9:01 p.m.