Triple
T63709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UDP |
E1266
|
entity |
| Predicate | flowControl |
P3686
|
FINISHED |
| Object | no flow control |
—
|
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: no flow control | Statement: [UDP, flowControl, no flow control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowControl Context triple: [UDP, flowControl, no flow control]
-
A.
fareControl
Indicates that an entity is responsible for monitoring, enforcing, or managing payment of fares for access to a service or facility.
-
B.
outflow
Indicates the movement or discharge of something from an origin or source to the outside or to another location.
-
C.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
D.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
E.
operationalCeiling
Indicates the maximum altitude at which an entity (such as an aircraft or system) is designed or permitted to operate effectively and safely.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24ea3c44081908fa3856969881d1f |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24fcf5a88819088c5fa4c08476358 |
completed | Feb. 28, 2026, 2:15 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.