Triple
T31945679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H 81 |
E815644
|
entity |
| Predicate | appliesToOutput |
P1129
|
FINISHED |
| Object | thematic catalogue entries for Berlioz |
—
|
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: thematic catalogue entries for Berlioz | Statement: [H 81, appliesToOutput, thematic catalogue entries for Berlioz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToOutput Context triple: [H 81, appliesToOutput, thematic catalogue entries for Berlioz]
-
A.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
supportsOutputType
Indicates that one entity is capable of producing, handling, or generating data or results of the specified output type.
-
C.
hasOutputType
Indicates that an entity produces, returns, or yields a result of a specified type.
-
D.
outputIs
Indicates that one entity functions as the result, product, or outcome produced by another entity or process.
-
E.
outputsTo
Indicates that the result or data produced by one entity is directed or sent to another entity as its destination or target.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: May 1, 2026, 12:06 a.m.