Triple
T22374662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jade template engine |
E553122
|
entity |
| Predicate | previousNpmPackageName |
P147411
|
FINISHED |
| Object | jade |
—
|
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: jade | Statement: [Jade template engine, previousNpmPackageName, jade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNpmPackageName Context triple: [Jade template engine, previousNpmPackageName, jade]
-
A.
previousNamespace
Indicates that one namespace directly precedes or was used before another namespace, typically in a versioning or migration context.
-
B.
predecessorVersion
Indicates that one entity is an earlier or prior version in a version sequence relative to another entity.
-
C.
previousSymbol
Indicates that one symbol directly precedes another symbol in a defined sequence or ordering.
-
D.
previousSystemName
Indicates that an entity was formerly known by a different system name prior to its current designation.
-
E.
previousComponent
Indicates that one component directly precedes another in an ordered sequence or structure.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15806b534819083716c2b090ede42 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342e9a0081909257210a81c96b29 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:45 p.m.