Triple
T10826286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C90 |
E255504
|
entity |
| Predicate | includesLibraryHeader |
P95944
|
FINISHED |
| Object | stdio.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: stdio.h | Statement: [C90, includesLibraryHeader, stdio.h]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesLibraryHeader Context triple: [C90, includesLibraryHeader, stdio.h]
-
A.
hasOfficialLibrary
Indicates that an entity possesses or is served by a formally recognized, authorized library.
-
B.
isMainLibraryOf
Indicates that a library serves as the primary or central library for a given organization, system, or collection.
-
C.
implementedInLibrary
Indicates that a particular functionality, feature, or component is realized and provided within a specific software library.
-
D.
includeUses
Indicates that one entity incorporates or relies on another entity as a component, resource, or dependency in its use or operation.
-
E.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d1c24881909f56d56207cccbef |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:19 p.m.