Triple
T1612429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JScript .NET |
E34641
|
entity |
| Predicate | compilerName |
P3924
|
FINISHED |
| Object | jsc.exe |
—
|
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: jsc.exe | Statement: [JScript .NET, compilerName, jsc.exe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilerName Context triple: [JScript .NET, compilerName, jsc.exe]
-
A.
compiler
chosen
Indicates that one entity serves as a compiler of another, typically transforming source material (such as code or documents) into a compiled or aggregated form.
-
B.
compilerPseudonymUsedBy
Indicates that a particular pseudonym is used as an alternate name or alias by a specific compiler.
-
C.
compiledUnder
Indicates that something (typically code or a program) was built or translated into executable form using a specific compiler, configuration, or compilation environment.
-
D.
compilationType
Indicates the specific method or mode by which something is compiled or assembled into a final form.
-
E.
editorName
Indicates the relationship that specifies the name of an editor associated with a given entity.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a93fa6926081908bc78d15c0be3185 |
completed | March 5, 2026, 8:32 a.m. |
| PD | Predicate disambiguation | batch_69a907c35f848190a2428c52e81d013e |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.