Triple
T35427235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priority-based Flow Control |
E1023953
|
entity |
| Predicate | pauses |
P142670
|
FINISHED |
| Object | selected traffic priorities |
—
|
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: selected traffic priorities | Statement: [Priority-based Flow Control, pauses, selected traffic priorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pauses Context triple: [Priority-based Flow Control, pauses, selected traffic priorities]
-
A.
halted
Indicates that an ongoing process, action, or movement has been stopped or brought to an end.
-
B.
laps
Indicates that one entity moves around another entity or a course, typically completing a circuit or overtaking it.
-
C.
restOn
Indicates that one entity is physically supported by and in contact with the surface of another entity, typically in a stable, stationary position.
-
D.
slows
chosen
Indicates that one entity causes another entity’s speed, rate, or progress to decrease.
-
E.
cooldown
Indicates that an entity must wait a specified period of time before performing the same action or a related action again.
- 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_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. |
Created at: May 3, 2026, 4:03 p.m.