Triple
T34595170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | stddef.h |
E888287
|
entity |
| Predicate | ptrdiff_tIsUsedFor |
P49064
|
FINISHED |
| Object | difference between pointers |
—
|
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: difference between pointers | Statement: [stddef.h, ptrdiff_tIsUsedFor, difference between pointers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ptrdiff_tIsUsedFor Context triple: [stddef.h, ptrdiff_tIsUsedFor, difference between pointers]
-
A.
usedInIndex
Indicates that something is utilized or referenced within a particular index or indexing structure.
-
B.
isUsedToCompute
chosen
Indicates that one entity serves as an input, basis, or resource for performing a calculation or deriving a result about another entity.
-
C.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as another entity.
-
D.
indexUsedBy
Indicates that a particular index is utilized or referenced by another entity, such as a query, process, or data structure.
-
E.
isInUse
Indicates that an entity is currently being utilized or actively engaged in its intended function or operation.
- 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.