Triple
T5421609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 768 |
E121262
|
entity |
| Predicate | checksumUsage |
P5658
|
FINISHED |
| Object | optional in IPv4 |
—
|
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: optional in IPv4 | Statement: [RFC 768, checksumUsage, optional in IPv4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checksumUsage Context triple: [RFC 768, checksumUsage, optional in IPv4]
-
A.
checksum
Indicates that a value has been computed from data to verify its integrity or detect errors in transmission or storage.
-
B.
supportsJournalChecksumming
Indicates that an entity provides functionality to compute and verify checksums for journal data to ensure its integrity.
-
C.
usesIntegrityCheck
chosen
Indicates that an entity employs a mechanism to verify the integrity or correctness of data, code, or operations.
-
D.
usesScrambling
Indicates that one entity applies a scrambling process or technique to another entity or to information associated with it.
-
E.
hasCheckDigit
Indicates that an identifier or code includes a calculated check digit used to verify its correctness or integrity.
- 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_69bd463b58d88190b258261573de9e91 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87eac41481908a4982db5d119edd |
completed | March 20, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.