Triple
T35427236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priority-based Flow Control |
E1023953
|
entity |
| Predicate | doesNotPause |
P182968
|
FINISHED |
| Object | entire link |
—
|
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: entire link | Statement: [Priority-based Flow Control, doesNotPause, entire link]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotPause Context triple: [Priority-based Flow Control, doesNotPause, entire link]
-
A.
doesNotPreempt
Indicates that one action, event, or rule does not take priority over, override, or occur in place of another.
-
B.
doesNotPrevent
Indicates that one entity or condition fails to stop, block, or inhibit another event, action, or state from occurring.
-
C.
doesNotTry
Indicates that an entity makes no attempt to perform a particular action or engage in a specified activity.
-
D.
doesNot
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
- F. None of above. chosen
Provenance (4 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795933588819082ba3c1716b05d63 |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.