Triple
T28616333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WaitForMultipleObjects |
E724280
|
entity |
| Predicate | maximumObjectCount |
P177132
|
FINISHED |
| Object | MAXIMUM_WAIT_OBJECTS |
—
|
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: MAXIMUM_WAIT_OBJECTS | Statement: [WaitForMultipleObjects, maximumObjectCount, MAXIMUM_WAIT_OBJECTS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumObjectCount Context triple: [WaitForMultipleObjects, maximumObjectCount, MAXIMUM_WAIT_OBJECTS]
-
A.
maximumEntries
Indicates the relationship that specifies the highest number of entries that are allowed or supported in a given context.
-
B.
maxNumberOfValues
Indicates the maximum count of distinct values that may be associated with a given entity or property in this relationship.
-
C.
maximumCapacity
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
D.
maxStackSize
Indicates the maximum number of identical items or elements that can be grouped or stacked together as a single unit.
-
E.
maximumVolumeSize
Indicates the largest allowable size or capacity that a volume can have within a given system or context.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6f85bfba48190aba95b40642a8ca7 |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f854486c81909396d944a55e03ab |
completed | May 3, 2026, 7:25 a.m. |
Created at: April 28, 2026, 4:32 a.m.