Triple
T17677271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1.1.1.1 DNS resolver |
E440671
|
entity |
| Predicate | IPv6Address |
P98689
|
FINISHED |
| Object | 2606:4700:4700::1111 |
—
|
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: 2606:4700:4700::1111 | Statement: [1.1.1.1 DNS resolver, IPv6Address, 2606:4700:4700::1111]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IPv6Address Context triple: [1.1.1.1 DNS resolver, IPv6Address, 2606:4700:4700::1111]
-
A.
addressFamily
Indicates the type of network address family (such as IPv4 or IPv6) associated with or used by an entity in a communication context.
-
B.
ipv6Deployment
Indicates that an entity has implemented, enabled, or supports IPv6 networking within its systems or infrastructure.
-
C.
addressPrefix
Indicates that one address string serves as the starting portion or leading segment of another address.
-
D.
hasIP
chosen
Indicates that one entity possesses, is assigned, or is associated with a specific IP address.
-
E.
addressPrefixMainnet
Indicates that an address has the prefix format used for the main (primary/production) network.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6e959c819092d9d33e79bd51f7 |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:01 a.m.