Triple
T17521455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Streamlit Community Cloud |
E426686
|
entity |
| Predicate | supportsDeploymentFrom |
P99180
|
FINISHED |
| Object | GitHub repositories |
—
|
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: GitHub repositories | Statement: [Streamlit Community Cloud, supportsDeploymentFrom, GitHub repositories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDeploymentFrom Context triple: [Streamlit Community Cloud, supportsDeploymentFrom, GitHub repositories]
-
A.
canDeployWith
Indicates that one entity is compatible or allowed to be deployed together with another entity in the same environment or configuration.
-
B.
canDeployAs
Indicates that one entity is capable of being deployed or instantiated in the role, form, or environment represented by another entity.
-
C.
canDeploy
Indicates that one entity has the permission or capability to deploy another entity (such as software, resources, or configurations) into a target environment.
-
D.
supportedFrom
chosen
Indicates that one entity provides backing, assistance, or justification for another entity, often serving as the source or basis of that support.
-
E.
canBeDeployedUnder
Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d2f79881909556894728e255ab |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:49 a.m.