Triple
T22650337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solid Testing Library |
E559073
|
entity |
| Predicate | testingStyle |
P43154
|
FINISHED |
| Object | behavior-focused testing |
—
|
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: behavior-focused testing | Statement: [Solid Testing Library, testingStyle, behavior-focused testing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testingStyle Context triple: [Solid Testing Library, testingStyle, behavior-focused testing]
-
A.
testingMethod
chosen
Indicates the procedure, technique, or approach used to perform a particular test or evaluation.
-
B.
testType
Indicates the specific category or kind of test associated with an entity or event.
-
C.
testedUnder
Indicates that one entity is examined, evaluated, or experimented on while being subject to the conditions, environment, or parameters specified by another entity.
-
D.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
-
E.
testStatus
Indicates the current outcome or state of a test, such as whether it has passed, failed, or is still in progress.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1703b40b88190aec5cf2fa28bfcbf |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:05 p.m.