Triple
T31358781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I. Introduzione e Allegro |
E799806
|
entity |
| Predicate | workStructureFunction |
P50478
|
FINISHED |
| Object | establishes thematic material |
—
|
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: establishes thematic material | Statement: [I. Introduzione e Allegro, workStructureFunction, establishes thematic material]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workStructureFunction Context triple: [I. Introduzione e Allegro, workStructureFunction, establishes thematic material]
-
A.
workStructure
chosen
Indicates how work is organized, arranged, or structured within or between entities.
-
B.
structureFunction
Indicates that one entity’s physical or organizational structure serves a particular function or role in relation to another entity.
-
C.
sourceWorkStructure
Indicates that one work serves as the structural or organizational basis for another work.
-
D.
refersToWorkStructure
Indicates that one entity references or is associated with a particular work-related organizational structure or framework.
-
E.
planStructure
Indicates that one entity defines or organizes the internal arrangement, components, or layout of another entity.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 29, 2026, 9:17 p.m.