Triple
T22444634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CJS |
E554833
|
entity |
| Predicate | supportsDefaultExport |
P203
|
FINISHED |
| Object | via assigning to module.exports |
—
|
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: via assigning to module.exports | Statement: [CJS, supportsDefaultExport, via assigning to module.exports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsDefaultExport Context triple: [CJS, supportsDefaultExport, via assigning to module.exports]
-
A.
hasMainExport
Indicates that one entity is the primary good or commodity exported by another entity.
-
B.
supportsModule
Indicates that one entity provides compatibility, functionality, or resources necessary for another entity’s module to operate or be used.
-
C.
supportsImportExport
Indicates that one entity provides functionality for importing and exporting data or resources to and from another entity.
-
D.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
isExportable
Indicates that something can be legally and practically transferred or sent out from one jurisdiction, system, or context to another.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae517208190924a7968723f55ef |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.