Triple
T27589526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | opendev.org |
E699760
|
entity |
| Predicate | primaryCodeReviewTool |
P199889
|
FINISHED |
| Object | Gerrit |
—
|
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: Gerrit | Statement: [opendev.org, primaryCodeReviewTool, Gerrit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryCodeReviewTool Context triple: [opendev.org, primaryCodeReviewTool, Gerrit]
-
A.
codeHostingService
Indicates a relationship where a platform provides hosting and management services for source code repositories and related development workflows.
-
B.
commonSoftwareTools
Indicates that the related entities use or are associated with the same software tools.
-
C.
supportsGitIntegration
Indicates that one entity provides functionality or compatibility that allows integration with Git for version control operations.
-
D.
compilerOrEditor
Indicates that one entity functions as a compiler or editor of the other entity, typically preparing, organizing, or revising its content.
-
E.
includesTooling
Indicates that one entity contains, provides, or comes bundled with specific tools or tooling capabilities related to another entity.
- F. None of above. chosen
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_69ef6a4d71f081909a1235763206b691 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69ff632176b0819084610ae2e57ab679 |
completed | May 9, 2026, 4:38 p.m. |
Created at: April 27, 2026, 2:05 p.m.