Triple
T10826860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osmocom project |
E255516
|
entity |
| Predicate | codeHostingPlatform |
P55144
|
FINISHED |
| Object | git-based 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: git-based repositories | Statement: [Osmocom project, codeHostingPlatform, git-based repositories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeHostingPlatform Context triple: [Osmocom project, codeHostingPlatform, git-based repositories]
-
A.
codeHostingService
chosen
Indicates a relationship where a platform provides hosting and management services for source code repositories and related development workflows.
-
B.
codeSpace
Indicates the namespace or contextual scope within which a piece of code, identifier, or programming element is defined and interpreted.
-
C.
repositoryType
Indicates the kind or classification of a repository associated with an entity.
-
D.
softwareDomain
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
-
E.
studioHost
Indicates that one entity serves as the host or presenter within a studio setting for another entity or program.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d734d1c24881909f56d56207cccbef |
completed | April 9, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.