Triple
T9689801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold en Italie |
E234507
|
entity |
| Predicate | orchestrationIncludes |
P89641
|
FINISHED |
| Object | orchestra |
—
|
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: orchestra | Statement: [Harold en Italie, orchestrationIncludes, orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orchestrationIncludes Context triple: [Harold en Italie, orchestrationIncludes, orchestra]
-
A.
orchestration
Indicates the coordination and arrangement of multiple components or processes to work together harmoniously toward a unified outcome.
-
B.
orchestrationFor
Indicates a relationship where one entity coordinates, arranges, or manages the actions or interactions of another entity or set of entities to achieve a desired outcome.
-
C.
orchestrationDetail
Indicates the specific manner, parameters, or configuration by which an overarching process, workflow, or set of coordinated actions is organized and executed.
-
D.
orchestrationStyle
Indicates the manner or approach by which multiple components, services, or processes are coordinated and controlled to work together.
-
E.
orchestratedFor
Indicates that one entity planned, coordinated, or arranged something specifically on behalf of or for the benefit of another entity.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d02b20881909d7c0d5d6aaafcb0 |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd9408c848190b84dd74d87f76273 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:17 p.m.