Triple
T5770736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIPRNET |
E127324
|
entity |
| Predicate | isolatedFrom |
P39640
|
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: [SIPRNET, isolatedFrom, public Internet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isolatedFrom Context triple: [SIPRNET, isolatedFrom, public Internet]
-
A.
isolatedBy
chosen
Indicates that one entity has been separated or kept apart from another entity or set of entities, preventing interaction or influence between them.
-
B.
isIsolated
Indicates that an entity exists or occurs separately from others, without direct contact, interaction, or connection.
-
C.
separatedFromByLand
Indicates that two entities are divided or kept apart from each other by an intervening landmass.
-
D.
hasIsolation
Indicates that an entity is separated or kept apart from others, typically to prevent interaction, influence, or contamination.
-
E.
historicalIsolationFrom
Indicates that one entity has been historically separated or cut off from another entity, typically due to geographic, political, cultural, or social barriers over an extended period.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:50 p.m.