Triple
T1077179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAT64 |
E23865
|
entity |
| Predicate | usesAddressEmbedding |
P3704
|
FINISHED |
| Object | IPv4-embedded IPv6 addresses |
—
|
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-embedded IPv6 addresses | Statement: [NAT64, usesAddressEmbedding, IPv4-embedded IPv6 addresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAddressEmbedding Context triple: [NAT64, usesAddressEmbedding, IPv4-embedded IPv6 addresses]
-
A.
embeddingType
Indicates the specific kind or category of embedding representation used to encode an entity or data.
-
B.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
C.
hasAddress
Indicates that an entity is associated with a specific address or location.
-
D.
isStyleOfAddress
Indicates that one term or expression functions as a particular way of addressing or referring to another entity.
-
E.
supportsAddressTypes
chosen
Indicates that an entity is capable of handling or working with one or more specified types of addresses.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b94288d88190aae4fb86236c0702 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.