Triple
T30299741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network framework |
E770623
|
entity |
| Predicate | exposesType |
P169058
|
FINISHED |
| Object | NWConnection |
—
|
NE NERFINISHED |
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: NWConnection | Statement: [Network framework, exposesType, NWConnection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposesType Context triple: [Network framework, exposesType, NWConnection]
-
A.
exposureType
Indicates the specific manner or context in which one entity is exposed to another entity, condition, or influence.
-
B.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
C.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
D.
exposedThrough
Indicates that something becomes revealed, accessible, or affected as a result of passing through or being subjected to another thing or medium.
-
E.
exportsType
Indicates that one entity sends or sells a particular type or category of goods, services, or resources to another entity across a boundary (such as international borders).
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813976048190be49bb86744b2fb2 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:48 p.m.