Triple
T1077164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NAT64 |
E23865
|
entity |
| Predicate | enablesCommunicationBetween |
P23642
|
FINISHED |
| Object | IPv6-only clients |
—
|
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: IPv6-only clients | Statement: [NAT64, enablesCommunicationBetween, IPv6-only clients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enablesCommunicationBetween Context triple: [NAT64, enablesCommunicationBetween, IPv6-only clients]
-
A.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
B.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
-
C.
enablesNavigationBetween
Indicates that one entity provides the means or capability for moving or transitioning between two other entities or locations.
-
D.
regulatesTrafficBetween
Indicates that one entity controls, manages, or directs the flow of traffic occurring between two other entities or locations.
-
E.
connectivity
Indicates...the existence, degree, or quality of a link or communication pathway between entities, allowing interaction or information flow between them.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.