Triple
T32413985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | API Apps |
E828294
|
entity |
| Predicate | supportsDeploymentSource |
P31025
|
FINISHED |
| Object | GitHub |
E5697
|
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: GitHub | Statement: [API Apps, supportsDeploymentSource, GitHub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeploymentSource Context triple: [API Apps, supportsDeploymentSource, GitHub]
-
A.
deploymentSource
chosen
Indicates the origin or mechanism from which something is deployed, such as the system, process, or source responsible for initiating the deployment.
-
B.
canDeployWith
Indicates that one entity is compatible or allowed to be deployed together with another entity in the same environment or configuration.
-
C.
canDeployAs
Indicates that one entity is capable of being deployed or instantiated in the role, form, or environment represented by another entity.
-
D.
canDeploy
Indicates that one entity has the permission or capability to deploy another entity (such as software, resources, or configurations) into a target environment.
-
E.
supportsInstallation
Indicates that one entity is capable of enabling, handling, or being compatible with the installation of 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_69f34919f300819092b541c6277cd68a |
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_6a344f1fd52481908645912dec8d1953 |
completed | June 18, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:53 a.m.