Triple
T8823566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCCL |
E209960
|
entity |
| Predicate | primaryAPIStyle |
P31951
|
FINISHED |
| Object | C API |
—
|
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: C API | Statement: [NCCL, primaryAPIStyle, C API]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAPIStyle Context triple: [NCCL, primaryAPIStyle, C API]
-
A.
APIStyle
chosen
Indicates a relationship where something conforms to, follows, or is characterized by a particular application programming interface (API) style or design convention.
-
B.
protocolStyle
Indicates the manner or format in which a protocol or communication procedure is structured or expressed.
-
C.
APIType
Indicates the type or category of an API associated with or used by an entity.
-
D.
primaryStyle
Indicates the main or predominant style associated with an entity, distinguishing it from other secondary or supporting styles.
-
E.
hasAPIs
Indicates that one entity provides or exposes application programming interfaces (APIs) that can be used or accessed by another entity.
- 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_69ca8364e13081909c85fe80f44fe86f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc6030b25081909d67488b35a72e05 |
completed | April 1, 2026, midnight |
| PD | Predicate disambiguation | batch_69cc5c21e64c81908490e3b0875dc0d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:46 p.m.