Triple
T28996539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Age (HTTP header) |
E736180
|
entity |
| Predicate | canBeCappedAt |
P14460
|
FINISHED |
| Object | 2147483648 |
—
|
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: 2147483648 | Statement: [Age (HTTP header), canBeCappedAt, 2147483648]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeCappedAt Context triple: [Age (HTTP header), canBeCappedAt, 2147483648]
-
A.
mayBeCappedBy
Indicates that one entity can optionally serve as a covering or cap for another entity.
-
B.
isMostCappedFor
Indicates that one entity holds the record for having made the highest number of appearances (caps) for another entity, typically within a team or organization.
-
C.
canBeExceededIn
Indicates that one entity’s value, level, or extent is capable of being surpassed by that of another entity within a specified context.
-
D.
capped
Indicates that one entity has placed a limit or maximum boundary on another entity’s quantity, value, or extent.
-
E.
maximumCapacity
chosen
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 28, 2026, 9:31 a.m.