Triple
T22109364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIPRNET |
E546373
|
entity |
| Predicate | logicalSeparationFrom |
P90529
|
FINISHED |
| Object | public Internet |
—
|
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: public Internet | Statement: [NIPRNET, logicalSeparationFrom, public Internet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicalSeparationFrom Context triple: [NIPRNET, logicalSeparationFrom, public Internet]
-
A.
definedSeparationFrom
Indicates a formally specified distinction or boundary established between one entity and another.
-
B.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
-
C.
typeOfSeparation
chosen
Indicates the specific manner or category of separation that exists or occurred between entities.
-
D.
symbolicallySeparated
Indicates that two entities are kept apart or distinguished from each other in a conceptual, abstract, or representational (rather than physical) way.
-
E.
separatedIn
Indicates that two or more entities, once together or associated, have been divided, split, or otherwise placed into distinct parts, groups, or locations.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291b9c988190b3ddd06d1f40dc78 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.