Triple
T27589525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | opendev.org |
E699760
|
entity |
| Predicate | sourceCodeManagement |
P55144
|
FINISHED |
| Object | Git |
—
|
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: Git | Statement: [opendev.org, sourceCodeManagement, Git]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sourceCodeManagement Context triple: [opendev.org, sourceCodeManagement, Git]
-
A.
codeHostingService
chosen
Indicates a relationship where a platform provides hosting and management services for source code repositories and related development workflows.
-
B.
sourceCodeReleased
Indicates that the source code for a software project or component has been made publicly available or otherwise released for access.
-
C.
sourceCodeReleasedBy
Indicates that the source code of a software or project has been made publicly available by a specific releasing entity.
-
D.
repositoryBrowser
Indicates a tool or interface that allows users to view, navigate, and explore the contents of a repository.
-
E.
sharesCodebaseWith
Indicates that two software systems or components are built from, or depend on, substantially the same underlying source code.
- 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_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 2:05 p.m.