Triple
T28906456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4633 |
E733096
|
entity |
| Predicate | ipVersion |
P10653
|
FINISHED |
| Object | 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: IPv4 | Statement: [RFC 4633, ipVersion, IPv4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ipVersion Context triple: [RFC 4633, ipVersion, IPv4]
-
A.
usesIPProtocol
Indicates that one entity communicates or operates using a specific IP (Internet Protocol) version or protocol.
-
B.
protocolVersion
chosen
Indicates the specific version of a protocol that governs how two or more entities communicate or interact.
-
C.
protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
-
D.
protocolFamily
Indicates that one protocol belongs to, or is categorized under, a broader protocol family or group.
-
E.
hasIP
Indicates that one entity possesses, is assigned, or is associated with a specific IP address.
- 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_69f05b096d208190958a57d2e4b5a93a |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65adb06348190946beb0bbe268e4e |
completed | May 2, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:07 a.m.