Triple
T22445984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DDC |
E554862
|
entity |
| Predicate | invokedVia |
P39337
|
FINISHED |
| Object | dart compile js (for some workflows) |
—
|
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: dart compile js (for some workflows) | Statement: [DDC, invokedVia, dart compile js (for some workflows)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invokedVia Context triple: [DDC, invokedVia, dart compile js (for some workflows)]
-
A.
invokedIn
Indicates that an action, method, or function is called or executed within the context or body of another construct (such as a method, block, or scope).
-
B.
invocationOf
Indicates that one entity is the act, event, or instance of calling upon, summoning, or appealing to another entity (such as a function, service, or authority) to perform its role or be brought into effect.
-
C.
invocationType
chosen
Indicates the manner or mode in which an action, function, or process is called, triggered, or executed.
-
D.
calledAs
Indicates that one entity is referred to, named, or addressed by another specific name or label.
-
E.
calledBy
Indicates that one entity initiates a call or invocation to another 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4803908190990280ebd258cb03 |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.