Triple
T34569859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotgipfler |
E887595
|
entity |
| Predicate | qualityAssessment |
P96882
|
FINISHED |
| Object | high-quality |
—
|
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: high-quality | Statement: [Rotgipfler, qualityAssessment, high-quality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualityAssessment Context triple: [Rotgipfler, qualityAssessment, high-quality]
-
A.
evaluationAspect
chosen
Indicates the specific dimension or criterion of performance or quality that is being assessed within an evaluation.
-
B.
qualityScheme
Indicates that an entity is associated with a particular quality assurance or quality classification scheme that defines how its quality is evaluated or certified.
-
C.
quality
Indicates that an entity possesses a particular attribute, characteristic, or degree of excellence that defines how good, suitable, or effective it is in a given context.
-
D.
supportsQuality
Indicates that one entity contributes to maintaining, enhancing, or ensuring the quality or standard of another entity or process.
-
E.
recognisedQuality
Indicates that one entity acknowledges, identifies, or validates a particular quality or attribute present in 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:02 a.m.