Triple
T22375148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sails Company |
E553133
|
entity |
| Predicate | usesLanguageInProduct |
P108903
|
FINISHED |
| Object | JavaScript |
—
|
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: JavaScript | Statement: [The Sails Company, usesLanguageInProduct, JavaScript]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLanguageInProduct Context triple: [The Sails Company, usesLanguageInProduct, JavaScript]
-
A.
languageOfProduct
Indicates the language in which a product is written, labeled, presented, or otherwise made available.
-
B.
usesLanguageFor
chosen
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
C.
usesLanguageAs
Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
-
D.
usedInLanguage
Indicates that something (such as a word, expression, or symbol) is employed or occurs within a particular language.
-
E.
includesLanguage
Indicates that one entity contains, supports, or makes use of a specified language as part of its content, functionality, or representation.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15807cb748190abd9adc08ca1ad4f |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.