Triple
T25602797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slepian–Wolf coding theorem |
E641830
|
entity |
| Predicate | rateConstraint |
P158901
|
FINISHED |
| Object | R_X + R_Y ≥ H(X,Y) |
—
|
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: R_X + R_Y ≥ H(X,Y) | Statement: [Slepian–Wolf coding theorem, rateConstraint, R_X + R_Y ≥ H(X,Y)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rateConstraint Context triple: [Slepian–Wolf coding theorem, rateConstraint, R_X + R_Y ≥ H(X,Y)]
-
A.
rateConstraint
chosen
Indicates a limitation or bound on the rate at which a process, transaction, or interaction is allowed to occur.
-
B.
supportsRateLimiting
Indicates that one entity provides or is compatible with mechanisms to restrict the rate at which another entity can perform actions or process requests.
-
C.
rideLimit
Indicates a constraint on the maximum number, duration, or frequency of rides permitted for an entity.
-
D.
volumeLimitationBasis
Indicates the rule, criterion, or reference measure used as the basis for determining a limitation on volume.
-
E.
isRateLimitingIn
Indicates that one entity imposes or enforces rate limiting on operations occurring within, or directed 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f9a7d7d881909014fdf3746f981b |
completed | May 2, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 4:36 p.m.