Triple
T27733787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.ValueTuple |
E697486
|
entity |
| Predicate | supportsUpToElements |
P77172
|
FINISHED |
| Object | 8 |
—
|
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: 8 | Statement: [System.ValueTuple, supportsUpToElements, 8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsUpToElements Context triple: [System.ValueTuple, supportsUpToElements, 8]
-
A.
supportsCoreCountUpTo
Indicates that an entity is capable of functioning correctly with, or providing compatibility for, processor configurations up to a specified maximum number of cores.
-
B.
hasElementOrdersUpTo
chosen
Indicates that one entity includes or supports elements whose orders (e.g., magnitudes, degrees, or hierarchical levels) do not exceed a specified upper limit defined by the other entity.
-
C.
supportsSince
Indicates that one entity has been providing support to another entity starting from a specific point in time and continuing thereafter.
-
D.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
E.
supportsDeviceCount
Indicates the number of devices that a system, service, or component is capable of supporting concurrently.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffc605b0648190a7abe9128b0d857a |
completed | May 9, 2026, 11:40 p.m. |
| PD | Predicate disambiguation | batch_69ffc5742d80819099f947ece78d5700 |
completed | May 9, 2026, 11:38 p.m. |
Created at: April 27, 2026, 3:12 p.m.