Triple
T27589527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | opendev.org |
E699760
|
entity |
| Predicate | continuousIntegrationSystem |
P164280
|
FINISHED |
| Object | Zuul |
—
|
NE NERFINISHED |
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: Zuul | Statement: [opendev.org, continuousIntegrationSystem, Zuul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuousIntegrationSystem Context triple: [opendev.org, continuousIntegrationSystem, Zuul]
-
A.
supportsGitIntegration
Indicates that one entity provides functionality or compatibility that allows integration with Git for version control operations.
-
B.
integratesInfrastructure
Indicates that one entity combines or coordinates infrastructure components or systems of another entity into a unified, functioning whole.
-
C.
deploymentTool
chosen
Indicates a tool or system used to deploy, release, or distribute software or configurations to target environments.
-
D.
integratedIn
Indicates that one entity is incorporated as a component or part within a larger system, structure, or context represented by another entity.
-
E.
codeHostingService
Indicates a relationship where a platform provides hosting and management services for source code repositories and related development workflows.
- 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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 2:05 p.m.