Triple
T34594931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPython Git repository |
E888282
|
entity |
| Predicate | defaultBranch |
P43609
|
FINISHED |
| Object | main |
—
|
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: main | Statement: [CPython Git repository, defaultBranch, main]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultBranch Context triple: [CPython Git repository, defaultBranch, main]
-
A.
defaultBranchSupport
Indicates that an entity provides or has support for a designated default branch within a branching or version-control structure.
-
B.
defaultBranchNameHistorically
Indicates that the referenced branch name has historically served as the default branch for a repository or project, even if it may no longer be the current default.
-
C.
dominantBranch
Indicates that one branch in a branching structure is the primary or prevailing branch relative to the others.
-
D.
developedBranch
Indicates that one branch or offshoot was created, expanded, or evolved from another as its source or origin.
-
E.
centralBranch
chosen
Indicates that one entity functions as the main or primary branch within a larger organizational or structural system relative to another entity.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 2:03 a.m.