Triple
T32536460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun RPC |
E831601
|
entity |
| Predicate | typicalLanguageBindings |
P42338
|
FINISHED |
| Object | C |
E9269
|
NE 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 | Statement: [Sun RPC, typicalLanguageBindings, C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLanguageBindings Context triple: [Sun RPC, typicalLanguageBindings, C]
-
A.
typicalLanguages
chosen
Indicates the languages that are commonly or characteristically used, spoken, or associated with a given entity.
-
B.
primaryLanguageBinding
Indicates that one language or language-specific implementation is designated as the main or default binding for a given resource, interface, or functionality.
-
C.
supportsLanguageBindingSystem
Indicates that one entity provides mechanisms or infrastructure that enable another entity to create, use, or integrate language bindings for a system or platform.
-
D.
languageTargets
Indicates that a language is specifically directed at, intended for, or used to address a particular target entity (such as an audience, system, or domain).
-
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 (4 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a347064c28c8190b19791c61e8b034e |
completed | June 18, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:01 a.m.