Triple
T27755241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SysV message queues |
E701317
|
entity |
| Predicate | resourceLimitedBy |
P91382
|
FINISHED |
| Object | system-wide IPC limits |
—
|
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: system-wide IPC limits | Statement: [SysV message queues, resourceLimitedBy, system-wide IPC limits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceLimitedBy Context triple: [SysV message queues, resourceLimitedBy, system-wide IPC limits]
-
A.
limitedResource
Indicates that the related entity or quantity is finite, scarce, or constrained in availability or capacity.
-
B.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
C.
volumeLimitationBasis
Indicates the rule, criterion, or reference measure used as the basis for determining a limitation on volume.
-
D.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
E.
definesLimitOf
chosen
Indicates that one entity specifies or establishes the maximum or boundary condition applicable 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6375fa0bc8190be257d4d5eaa6dc7 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:23 p.m.