Triple
T17675911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TDD |
E440641
|
entity |
| Predicate | typicalTestLevel |
P31955
|
FINISHED |
| Object | unit tests |
—
|
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: unit tests | Statement: [TDD, typicalTestLevel, unit tests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTestLevel Context triple: [TDD, typicalTestLevel, unit tests]
-
A.
testingLevel
chosen
Indicates the degree or intensity to which something is examined, evaluated, or tested.
-
B.
typicalIntermediateLevel
Indicates that something represents a common or standard degree of difficulty, complexity, or proficiency that falls between beginner and advanced levels.
-
C.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
D.
typicalEquipmentLevel
Indicates the usual or standard amount or quality of equipment associated with an entity or situation.
-
E.
typicalLowestLevel
Indicates that something represents the most basic or minimal level that is commonly or normally found within a given context.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6cca54819094ea0bed1517724e |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10 a.m.