Triple
T17519164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YAGNI principle |
E426641
|
entity |
| Predicate | riskIfIgnored |
P127758
|
FINISHED |
| Object | bloated codebase |
—
|
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: bloated codebase | Statement: [YAGNI principle, riskIfIgnored, bloated codebase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskIfIgnored Context triple: [YAGNI principle, riskIfIgnored, bloated codebase]
-
A.
riskIfFailure
Indicates that one entity faces potential negative consequences or harm if another entity fails or an attempted action is unsuccessful.
-
B.
riskIfNoncompliance
Indicates that a risk or negative consequence will occur if the specified rules, requirements, or obligations are not complied with.
-
C.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
-
D.
riskIfBreached
Indicates that a breach of the referenced entity or condition would expose or create a potential risk or harm.
-
E.
riskElement
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
- F. None of above. chosen
Provenance (4 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_69d889dd9164819087b1dc3c9240c870 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d18c1c81908bb843bbddb44ca1 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.