Triple
T1774438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carbon (late transitional API) |
E38945
|
entity |
| Predicate | apiStyle |
P31951
|
FINISHED |
| Object | procedural 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: procedural C API | Statement: [Carbon (late transitional API), apiStyle, procedural C API]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: apiStyle Context triple: [Carbon (late transitional API), apiStyle, procedural 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.
APIType
Indicates the type or category of an API associated with or used by an entity.
-
C.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
D.
featuresStyle
Indicates that one entity exhibits, incorporates, or is characterized by a particular style associated with another entity.
-
E.
architecturalStyle
Indicates the architectural design tradition, movement, or style that characterizes the form and appearance of a structure or built work.
- 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb45402688190b9a535b14030c354 |
completed | March 7, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69abafd6a9948190ac2b2743db6f8f69 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:31 p.m.