Triple
T27735151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Net.CookieContainer |
E697511
|
entity |
| Predicate | defaultCapacity |
P172120
|
FINISHED |
| Object | 300 |
—
|
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: 300 | Statement: [System.Net.CookieContainer, defaultCapacity, 300]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultCapacity Context triple: [System.Net.CookieContainer, defaultCapacity, 300]
-
A.
originalCapacity
Indicates the initial or designed maximum amount or volume that something can hold, process, or produce before any changes or adjustments.
-
B.
currentCapacity
Indicates the present amount of capacity an entity is using or able to provide at a given time.
-
C.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
D.
earlyCapacities
Indicates that an entity possesses foundational abilities or skills that emerge at an initial or early stage of development or process.
-
E.
laterCapacity
Indicates that one entity’s capacity or capability occurs, becomes available, or is realized at a later time than another’s.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 27, 2026, 3:12 p.m.