Triple
T22374242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quasar plugins |
E553113
|
entity |
| Predicate | executionOrder |
P113075
|
FINISHED |
| Object | can be controlled via configuration |
—
|
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: can be controlled via configuration | Statement: [Quasar plugins, executionOrder, can be controlled via configuration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: executionOrder Context triple: [Quasar plugins, executionOrder, can be controlled via configuration]
-
A.
executionOrderedAtRequestOf
Indicates that an execution was carried out according to the wishes or formal request made by a specific party.
-
B.
operationSequence
chosen
Indicates that one operation occurs in a specific order relative to another within a defined sequence of actions.
-
C.
subsequentOrder
Indicates that one order occurs after or follows another order in sequence.
-
D.
orderOf
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
E.
establishedInOrder
Indicates that one entity was created, founded, or formally set up as a result of, or in accordance with, a specific order, directive, or mandate.
- 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_69f15806b534819083716c2b090ede42 |
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.