Triple
T22444633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CJS |
E554833
|
entity |
| Predicate | supportsNamedExports |
P148223
|
FINISHED |
| Object | via properties on 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 properties on module.exports | Statement: [CJS, supportsNamedExports, via properties on module.exports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNamedExports Context triple: [CJS, supportsNamedExports, via properties on module.exports]
-
A.
hasMainExport
Indicates that one entity is the primary good or commodity exported by another entity.
-
B.
otherExports
Indicates that an entity exports additional goods or services beyond its primary or specifically listed export categories.
-
C.
exportedAs
Indicates that something is made available or delivered to an external destination under a specified name, format, or representation.
-
D.
supportsModule
Indicates that one entity provides compatibility, functionality, or resources necessary for another entity’s module to operate or be used.
-
E.
supportsNameType
Indicates that one entity is capable of handling, recognizing, or being associated with a particular type or category of name.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.