Triple
T34595186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | stddef.h |
E888287
|
entity |
| Predicate | headerKind |
P25789
|
FINISHED |
| Object | fundamental types header |
—
|
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: fundamental types header | Statement: [stddef.h, headerKind, fundamental types header]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headerKind Context triple: [stddef.h, headerKind, fundamental types header]
-
A.
headerCategory
Indicates that one entity serves as a categorical grouping or classification for the header or heading represented by the other entity.
-
B.
header
Indicates that one entity serves as a heading or title section that precedes and organizes the content of another entity.
-
C.
headerField
Indicates that one entity is a specific header field (such as a name–value pair) belonging to or defined within another entity, typically a message, request, or document header.
-
D.
headerSignature
Indicates that a header includes a cryptographic or formal signature that authenticates or validates the header’s contents.
-
E.
headType
chosen
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:03 a.m.