Triple
T33204673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIVector |
E849989
|
entity |
| Predicate | supportsNSCoding |
—
|
GENERATED |
| Object | true |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNSCoding Context triple: [CIVector, supportsNSCoding, true]
-
A.
supportsSerialization
chosen
Indicates that an entity is capable of being converted to and from a serialized form for storage or transmission.
-
B.
supportsBlockBasedCoding
Indicates that an entity provides or enables functionality for creating programs using a block-based visual coding interface.
-
C.
supportedClass
Indicates that one entity is a class or type that is recognized, handled, or operable within the capabilities or context provided by another entity.
-
D.
supportsImplementationOf
Indicates that one entity provides the necessary resources, framework, or assistance for another entity to be carried out, realized, or put into practice.
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- F. None of above.
Provenance (1 batch)
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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:30 a.m.