Triple
T4277306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCA (scikit-learn) |
E97073
|
entity |
| Predicate | modulePath |
P3635
|
FINISHED |
| Object | sklearn.decomposition.PCA |
—
|
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: sklearn.decomposition.PCA | Statement: [PCA (scikit-learn), modulePath, sklearn.decomposition.PCA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modulePath Context triple: [PCA (scikit-learn), modulePath, sklearn.decomposition.PCA]
-
A.
moduloPatternName
Indicates that an entity is associated with a specific naming pattern used for modulo-based grouping or partitioning.
-
B.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
C.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
-
D.
ultimatePathTo
Indicates that one entity represents the final, most fundamental, or decisive route, method, or means by which another entity is reached or achieved.
-
E.
samplePathProperty
chosen
Indicates that there exists a representative or example path associated with an entity, capturing how it is typically traversed, accessed, or connected within a structure or system.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3501ef1388190b0c968b069014a59 |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.