Triple
T32013567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KL10 |
E817471
|
entity |
| Predicate | supportsParityChecking |
P178252
|
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, supportsParityChecking, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsParityChecking Context triple: [KL10, supportsParityChecking, yes]
-
A.
hasParity
Indicates that two entities share the same parity property (e.g., both even or both odd) with respect to a specified attribute or value.
-
B.
requiresParityFor
Indicates that one entity can only be used, applied, or valid when another entity has a specific parity condition (such as being even or odd).
-
C.
requiresParityBetween
Indicates that a balanced or matching condition must hold between two entities, such that their relevant attributes or quantities share the same parity or equivalence.
-
D.
hasParityPatterns
Indicates that there is a specific pattern or regularity in the parity (odd/even characteristics) associated with the related entities.
-
E.
supportsMemoryParity
chosen
Indicates that one entity provides or enables memory parity protection or compatibility for another entity’s memory operations.
- 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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:15 a.m.