Triple
T22643963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chôros |
E558905
|
entity |
| Predicate | hasInstrumentationRange |
P27293
|
FINISHED |
| Object | solo instrument |
—
|
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: solo instrument | Statement: [Chôros, hasInstrumentationRange, solo instrument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstrumentationRange Context triple: [Chôros, hasInstrumentationRange, solo instrument]
-
A.
hasInstrumentationProvidedBy
Indicates that the instrumentation used in an activity, process, or work is supplied or made available by a specified provider.
-
B.
hasMinimalInstrumentation
Indicates that an entity is associated with or characterized by using the smallest necessary amount of instrumentation or equipment.
-
C.
hasTypeOfInstrumentation
Indicates that one entity uses, involves, or is characterized by a particular type of instrumentation.
-
D.
hasRange
chosen
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
hasFrameworkInstrument
Indicates that one entity uses or is associated with a specific framework as the instrument or means for performing an action or achieving a result.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f170366ac881909e9d1dd2e7cf7a25 |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.