Triple
T29390250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SDUC |
E745352
|
entity |
| Predicate | supportsMaximumCapacity |
P14460
|
FINISHED |
| Object | 128 TB |
—
|
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: 128 TB | Statement: [SDUC, supportsMaximumCapacity, 128 TB]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMaximumCapacity Context triple: [SDUC, supportsMaximumCapacity, 128 TB]
-
A.
maximumCapacity
chosen
Indicates the greatest allowable or designed amount of something that an entity can hold, contain, or handle.
-
B.
hasCapacityTo
Indicates that one entity possesses the ability, power, or potential to perform an action or bring about a particular effect in relation to another entity or context.
-
C.
supportsMaxHeap
Indicates that one entity provides the necessary functionality or guarantees to correctly maintain and operate a max-heap data structure for another entity.
-
D.
capacityRecord
Indicates a recorded measure of how much of a resource, space, or system is available or can be utilized at a given time.
-
E.
supportsMaximumCurrent
Indicates that one entity is capable of handling or allowing a specified maximum electric current for another entity or connection.
- 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a03460f3a8c8190ae3f4cd69e0e54d9 |
completed | May 12, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_6a0345810b3481908aec06ab2b712e12 |
completed | May 12, 2026, 3:21 p.m. |
Created at: April 28, 2026, 2:41 p.m.