Triple
T31729144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WWV 111 |
E809806
|
entity |
| Predicate | catalogueSystemFor |
P69156
|
FINISHED |
| Object | complete works of Richard Wagner |
—
|
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: complete works of Richard Wagner | Statement: [WWV 111, catalogueSystemFor, complete works of Richard Wagner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: catalogueSystemFor Context triple: [WWV 111, catalogueSystemFor, complete works of Richard Wagner]
-
A.
catalogueSystem
chosen
Indicates a relationship where one entity serves as or belongs to a cataloging system that organizes, indexes, or classifies other entities.
-
B.
catalogueFor
Indicates that one entity serves as a catalog or organized listing that describes, indexes, or inventories another entity.
-
C.
catalogueSystemCreator
Indicates that an entity is the creator or originator of a particular catalogue system.
-
D.
catalogueType
Indicates the classification or category assigned to an item within a catalogue or cataloging system.
-
E.
catalogueAccess
Indicates that an entity has permission to view or interact with a specified catalogue or collection of items.
- 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_69f348e009c8819095d77df52c645b9c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 30, 2026, 11:21 p.m.