Triple
T38638278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GitLab Container Registry |
E937616
|
entity |
| Predicate | canBeSelfHostedOn |
P86781
|
FINISHED |
| Object | self-managed GitLab instances |
—
|
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: self-managed GitLab instances | Statement: [GitLab Container Registry, canBeSelfHostedOn, self-managed GitLab instances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSelfHostedOn Context triple: [GitLab Container Registry, canBeSelfHostedOn, self-managed GitLab instances]
-
A.
canBeDeployedUnder
Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined by another entity.
-
B.
mayBeHostedBy
chosen
Indicates that an entity has the possibility or option of being hosted or accommodated by another entity.
-
C.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
-
D.
canDeployAs
Indicates that one entity is capable of being deployed or instantiated in the role, form, or environment represented by another entity.
-
E.
canDeploy
Indicates that one entity has the permission or capability to deploy another entity (such as software, resources, or configurations) into a target environment.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffc704e1e88190884928a6a5c55a87 |
completed | May 9, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69ffc6b483d881908ad872e25fa6abc5 |
completed | May 9, 2026, 11:43 p.m. |
Created at: May 3, 2026, 4:32 p.m.