Triple
T34594932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CPython Git repository |
E888282
|
entity |
| Predicate | previousDefaultBranch |
P30259
|
FINISHED |
| Object | master |
—
|
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: master | Statement: [CPython Git repository, previousDefaultBranch, master]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousDefaultBranch Context triple: [CPython Git repository, previousDefaultBranch, master]
-
A.
previousBranch
Indicates that one branch directly precedes another in an ordered sequence of branches.
-
B.
defaultBranchSupport
Indicates that an entity provides or has support for a designated default branch within a branching or version-control structure.
-
C.
defaultBranchNameHistorically
chosen
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.
-
D.
previousServiceBranch
Indicates that an entity was formerly associated with or served in a specified service branch before its current one.
-
E.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
- 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_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 1, 2026, 2:03 a.m.