Triple
T29229824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BSD sockets API |
E741035
|
entity |
| Predicate | providesDataStructure |
P191574
|
FINISHED |
| Object | sockaddr |
—
|
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: sockaddr | Statement: [BSD sockets API, providesDataStructure, sockaddr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesDataStructure Context triple: [BSD sockets API, providesDataStructure, sockaddr]
-
A.
usesDataStructure
Indicates that one entity employs or relies on a particular data structure in its operation or implementation.
-
B.
storageStructure
Indicates a relationship where one entity serves as a physical or logical structure used to store or contain another entity.
-
C.
providesDataProduct
Indicates that one entity supplies or makes available a specific data product to another entity or system.
-
D.
definesStructure
Indicates that one entity specifies or determines the organizational form, composition, or arrangement of another entity.
-
E.
producesStructure
Indicates that one entity generates, forms, or creates a physical or conceptual structure as a result of its action or function.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: April 28, 2026, 12:18 p.m.