Triple
T8290311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GA Channel |
E193876
|
entity |
| Predicate | softwareMaturityLevel |
P53729
|
FINISHED |
| Object | production-ready |
—
|
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: production-ready | Statement: [GA Channel, softwareMaturityLevel, production-ready]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: softwareMaturityLevel Context triple: [GA Channel, softwareMaturityLevel, production-ready]
-
A.
isDevelopmentLevelFor
chosen
Indicates that one entity represents the development or maturity level assigned to, or characteristic of, another entity.
-
B.
hasStabilityLevel
Indicates that something possesses a particular degree or state of stability, often quantified or categorized along a defined scale.
-
C.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
-
D.
softwareProductLine
Indicates a relationship where a software product belongs to, or is part of, a broader software product line or family.
-
E.
hasStandardizationLevel
Indicates the degree or extent to which something conforms to an established standard or set of standardized criteria.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7c99fdd48190a3f304237be609a0 |
completed | March 31, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:52 p.m.