Triple
T28617000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WSARecvFrom |
E724293
|
entity |
| Predicate | headerRequirement |
P90349
|
FINISHED |
| Object | include <winsock2.h> |
—
|
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: include <winsock2.h> | Statement: [WSARecvFrom, headerRequirement, include <winsock2.h>]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headerRequirement Context triple: [WSARecvFrom, headerRequirement, include <winsock2.h>]
-
A.
titleHolderRequirement
Indicates that a certain condition or set of conditions must be met in order for an entity to hold or retain a particular title.
-
B.
header
Indicates that one entity serves as a heading or title section that precedes and organizes the content of another entity.
-
C.
noticeRequirement
Indicates that one party is obligated to provide advance notification to another party before a specified action, change, or event occurs.
-
D.
requiredTo
chosen
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
E.
headCondition
Indicates that an entity has a specific condition, state, or attribute affecting its head.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 4:32 a.m.