Triple
T21802596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LSP PDU |
E538272
|
entity |
| Predicate | integrityMechanism |
P5658
|
FINISHED |
| Object | checksum |
—
|
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: checksum | Statement: [LSP PDU, integrityMechanism, checksum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integrityMechanism Context triple: [LSP PDU, integrityMechanism, checksum]
-
A.
providesIntegrity
Indicates that one entity ensures the correctness, consistency, and protection from unauthorized alteration of another entity or its data.
-
B.
usesIntegrityCheck
chosen
Indicates that an entity employs a mechanism to verify the integrity or correctness of data, code, or operations.
-
C.
requiresMACForIntegrity
Indicates that the action or relationship is only considered to provide integrity if a Message Authentication Code (MAC) is used.
-
D.
reliabilityMechanism
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
-
E.
integrity
Indicates that an entity or relationship maintains wholeness, consistency, and freedom from corruption or unauthorized alteration.
- 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0780062688190a6c3a2a0364f0f77 |
completed | April 28, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e6be751ce881909badced245ef76c7 |
completed | April 21, 2026, 12:01 a.m. |
Created at: April 16, 2026, 6:53 p.m.