Triple
T34541441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OsmoBSC |
E886816
|
entity |
| Predicate | repositoryMirror |
P19960
|
FINISHED |
| Object | GitHub |
—
|
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: GitHub | Statement: [OsmoBSC, repositoryMirror, GitHub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repositoryMirror Context triple: [OsmoBSC, repositoryMirror, GitHub]
-
A.
hasRepositoryMirror
chosen
Indicates that one repository serves as a mirrored copy or synchronized duplicate of another repository.
-
B.
trialMirrors
Indicates that one trial serves as a mirror or counterpart to another trial, reflecting its conditions, structure, or outcomes for comparison or replication purposes.
-
C.
repositoryUrl
Indicates the web address where the related code, data, or resources are stored and managed in a version-controlled repository.
-
D.
mirrorsDataFrom
Indicates that one entity replicates and keeps its data synchronized with the data of another entity, acting as a reflective copy.
-
E.
registryURL
Indicates the web address where an entity’s official registration information is stored or can be accessed.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71ff6a6d48190b84bd9e1cc217e70 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.