Triple
T22489066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QUnit |
E555966
|
entity |
| Predicate | testDefinitionPattern |
P123302
|
FINISHED |
| Object | function-based 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: function-based tests | Statement: [QUnit, testDefinitionPattern, function-based tests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testDefinitionPattern Context triple: [QUnit, testDefinitionPattern, function-based tests]
-
A.
jobDefinitionPattern
Indicates a recurring or standardized configuration that defines how a particular job or task should be structured or executed.
-
B.
definesMessagePattern
Indicates that one entity specifies or establishes the structural pattern or format that another message or set of messages should follow.
-
C.
languagePattern
Indicates a recurring or structured way in which language is used, organized, or formed within a given context.
-
D.
hasPattern
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
E.
testMatches
chosen
Indicates that a given test case or pattern corresponds to, satisfies, or correctly aligns with a specified input, condition, or expected outcome.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3f3b4c819092bfe6495c61db46 |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.