Triple
T22808139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moldovan Internet |
E564594
|
entity |
| Predicate | usesIPProtocol |
P149796
|
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: [Moldovan Internet, usesIPProtocol, IPv4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIPProtocol Context triple: [Moldovan Internet, usesIPProtocol, IPv4]
-
A.
usesIP
Indicates that one entity makes use of, operates through, or is associated with a particular IP address.
-
B.
usesIPFrom
Indicates that one entity operates or communicates using an IP address that originates from or is assigned to another entity.
-
C.
usedInProtocol
Indicates that something (e.g., a method, component, or resource) is employed as part of the steps or structure of a specific protocol.
-
D.
hasIP
Indicates that one entity possesses, is assigned, or is associated with a specific IP address.
-
E.
targetsProtocol
Indicates that one entity is designed to interact with, affect, or be applied to a specific protocol.
- 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5e0b088190ad0b9cc0d5aa1d96 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:32 p.m.