Triple
T27662414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chubby lock service |
E697153
|
entity |
| Predicate | languageOfAPI |
P167688
|
FINISHED |
| Object | C++ client library |
—
|
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++ client library | Statement: [Chubby lock service, languageOfAPI, C++ client library]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfAPI Context triple: [Chubby lock service, languageOfAPI, C++ client library]
-
A.
apiLanguage
chosen
Indicates that an entity uses, supports, or is implemented in a particular application programming interface (API) language.
-
B.
languageOfEndpoints
Indicates that the related entities use or are associated with the same language at their respective endpoints in a communication or interaction.
-
C.
languageOfInterface
Indicates the language used by or presented in a user interface.
-
D.
languageOfDocumentation
Indicates the language in which the documentation for an entity is written or provided.
-
E.
languageProvision
Indicates that one entity supplies, supports, or makes available a particular language (or set of languages) for use 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 27, 2026, 2:37 p.m.