Triple
T9313020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D-root |
E224049
|
entity |
| Predicate | hasIPv4Address |
P63813
|
FINISHED |
| Object | 199.7.91.13 |
—
|
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: 199.7.91.13 | Statement: [D-root, hasIPv4Address, 199.7.91.13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIPv4Address Context triple: [D-root, hasIPv4Address, 199.7.91.13]
-
A.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
B.
hasPublicAddressSystem
Indicates that an entity is equipped with or includes a public address (PA) system for broadcasting audio announcements.
-
C.
usesMulticastAddress
Indicates that one entity communicates or operates using a multicast network address to reach multiple recipients simultaneously.
-
D.
addressFamily
Indicates the type of network address family (such as IPv4 or IPv6) associated with or used by an entity in a communication context.
-
E.
usesIP
chosen
Indicates that one entity makes use of, operates through, or is associated with a particular 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b048a081909fd7ec0b6b863063 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.