Triple
T22813105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | @sveltejs/adapter-auto |
E565033
|
entity |
| Predicate | selectsBasedOn |
P136
|
FINISHED |
| Object | current environment |
—
|
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: current environment | Statement: [@sveltejs/adapter-auto, selectsBasedOn, current environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectsBasedOn Context triple: [@sveltejs/adapter-auto, selectsBasedOn, current environment]
-
A.
selectsFor
Indicates that one entity chooses or designates another entity as the preferred or targeted option from a set of possible candidates.
-
B.
selectedWith
Indicates that one entity is chosen or picked in conjunction with, or as part of a set including, another entity.
-
C.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
D.
selectionFrom
Indicates that one entity is chosen as a member or subset from a larger set or collection represented by another entity.
-
E.
alsoSelects
Indicates that an entity chooses or includes an additional option or item in conjunction with another already selected option or item.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d61c6f081908d3911710b3aff51 |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.