Triple
T32013566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KL10 |
E817471
|
entity |
| Predicate | designedForHighReliability |
P95504
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [KL10, designedForHighReliability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForHighReliability Context triple: [KL10, designedForHighReliability, yes]
-
A.
designedForHighCapacity
Indicates that something is intentionally created or configured to handle a large volume, load, or throughput.
-
B.
reliabilityCharacteristic
chosen
Indicates that one entity specifies or embodies a reliability-related property, feature, or performance attribute of another entity.
-
C.
reliabilityHigherThan
Indicates that one entity is considered to have greater reliability than another entity.
-
D.
reliabilityMechanism
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
-
E.
isHighPerformance
Indicates that an entity operates at a superior or above-standard level of efficiency, speed, or capability compared to typical expectations or benchmarks.
- 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
Created at: May 1, 2026, 12:15 a.m.