Triple
T28331322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballades |
E717544
|
entity |
| Predicate | technicalCharacteristics |
P128001
|
FINISHED |
| Object | demanding passagework |
—
|
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: demanding passagework | Statement: [Ballades, technicalCharacteristics, demanding passagework]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technicalCharacteristics Context triple: [Ballades, technicalCharacteristics, demanding passagework]
-
A.
equipmentCharacteristic
Indicates that a specific characteristic, property, or attribute is associated with a piece of equipment.
-
B.
codeCharacteristic
Indicates that one piece of code possesses a specific property, feature, or quality in relation to another referenced aspect.
-
C.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
D.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
E.
entityCharacteristic
chosen
Indicates that an entity possesses, exhibits, or is defined by a particular characteristic or attribute.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 12:32 a.m.