Triple
T25163193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bun test runner |
E626496
|
entity |
| Predicate | supportsFilePattern |
P29142
|
FINISHED |
| Object | *.test.ts |
—
|
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: *.test.ts | Statement: [Bun test runner, supportsFilePattern, *.test.ts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFilePattern Context triple: [Bun test runner, supportsFilePattern, *.test.ts]
-
A.
supportsPatternType
chosen
Indicates that one entity is compatible with, or capable of handling, a specified pattern type.
-
B.
hasPattern
Indicates that one entity exhibits, follows, or is characterized by a specific recurring form, structure, or design defined by another entity.
-
C.
patternSupport
Indicates that one entity provides evidence, validation, or reinforcement for the existence, correctness, or applicability of a particular pattern associated with another entity.
-
D.
supportsMultipleFiles
Indicates that the subject is capable of handling, processing, or operating on more than one file at the same time.
-
E.
supportsExtentsForFiles
Indicates that a system or component provides support for managing or using extent-based storage structures specifically for files.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 18, 2026, 6:31 a.m.