Triple
T12020775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | libclang |
E286141
|
entity |
| Predicate | supportsLanguageFamily |
P64840
|
FINISHED |
| Object | C-family languages |
—
|
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-family languages | Statement: [libclang, supportsLanguageFamily, C-family languages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLanguageFamily Context triple: [libclang, supportsLanguageFamily, C-family languages]
-
A.
usesLanguageFamily
chosen
Indicates that an entity communicates or operates using a language that belongs to a specified language family.
-
B.
isInLanguageFamily
Indicates that a language belongs to, or is classified within, a particular language family based on shared linguistic ancestry or characteristics.
-
C.
includesMajorLanguageFamily
Indicates that one entity encompasses, contains, or is associated with a major language family as part of its scope or classification.
-
D.
languageFamilyAssociated
Indicates that there is an association or connection between a language and a particular language family.
-
E.
usesLanguageSubfamily
Indicates that one entity communicates or operates using a language that belongs to a specified language subfamily.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.