Triple
T22444627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CJS |
E554833
|
entity |
| Predicate | defaultTypeInNodeWithoutField |
P1595
|
FINISHED |
| Object | commonjs |
—
|
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: commonjs | Statement: [CJS, defaultTypeInNodeWithoutField, commonjs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultTypeInNodeWithoutField Context triple: [CJS, defaultTypeInNodeWithoutField, commonjs]
-
A.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
B.
fieldType
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
-
C.
numericTypeFocus
Indicates that the relationship or context specifically concerns the numeric type or numerical aspect of the associated entities or values.
-
D.
hasNodeType
chosen
Indicates that an entity is associated with, or classified as, a specific type of node within a structured system or model.
-
E.
definedInField
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
- 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.