Triple
T27732540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codice Software |
E697463
|
entity |
| Predicate | hasPrimaryProductCategory |
P2767
|
FINISHED |
| Object | version control system |
—
|
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: version control system | Statement: [Codice Software, hasPrimaryProductCategory, version control system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryProductCategory Context triple: [Codice Software, hasPrimaryProductCategory, version control system]
-
A.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
B.
hasMajorCategory
chosen
Indicates that something is associated with or classified under a primary, overarching category.
-
C.
hasBodelCategory
Indicates that an entity is associated with a specific Bodel classification category within a defined categorization system.
-
D.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
E.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 27, 2026, 3:12 p.m.