Triple
T264656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GitHub |
E5697
|
entity |
| Predicate | providesAPI |
P1395
|
FINISHED |
| Object | REST 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: REST API | Statement: [GitHub, providesAPI, REST API]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesAPI Context triple: [GitHub, providesAPI, REST API]
-
A.
providedFor
Indicates that one entity supplies, furnishes, or makes something available to or on behalf of another entity for its use or benefit.
-
B.
availableAs
chosen
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
C.
commonlyImplementedBy
Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing entities.
-
D.
providesProperty
Indicates that one entity supplies, grants, or makes a particular property or attribute available to another entity.
-
E.
implementedUnder
Indicates that an action, policy, or process is carried out within the scope, authority, or framework defined by a particular higher-level plan, rule, or governing 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d8f9bbc8190a13841e4de093a66 |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6e07748190834022a65ba6d803 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.