Triple
T5480125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QCI (QoS Class Identifier) |
E123447
|
entity |
| Predicate | hasValueRange |
P27293
|
FINISHED |
| Object | 1–9 (original standardized QCIs) |
—
|
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: 1–9 (original standardized QCIs) | Statement: [QCI (QoS Class Identifier), hasValueRange, 1–9 (original standardized QCIs)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasValueRange Context triple: [QCI (QoS Class Identifier), hasValueRange, 1–9 (original standardized QCIs)]
-
A.
hasRange
chosen
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
B.
hasValue
Indicates that an entity is associated with a specific numerical, textual, or otherwise defined value.
-
C.
hasMinimumValue
Indicates that an entity possesses a value that is the lowest permissible or observed within a specified set, range, or context.
-
D.
hasLengthRange
Indicates that an entity’s length falls within a specified minimum-to-maximum range.
-
E.
hasColorRange
Indicates that an entity possesses or is associated with a specific span or set of colors, rather than a single discrete color.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9248ca348190aa116cace0f9b07a |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.