Triple
T30299930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSArray |
E770627
|
entity |
| Predicate | nullabilityAnnotation |
P163129
|
FINISHED |
| Object | nullable elements |
—
|
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: nullable elements | Statement: [NSArray, nullabilityAnnotation, nullable elements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nullabilityAnnotation Context triple: [NSArray, nullabilityAnnotation, nullable elements]
-
A.
isNullable
chosen
Indicates whether a value, field, or parameter is allowed to be null (i.e., have no assigned value).
-
B.
nullValueSupport
Indicates that the relationship or operation explicitly allows, handles, or preserves null (missing) values for the involved entities or attributes.
-
C.
Null
Indicates that no specific relationship or action is defined or applicable in this context.
-
D.
nullKeySupport
Indicates that the relationship or operation remains valid or supported even when the associated key or identifier is null.
-
E.
notatedWith
Indicates that something is represented, marked, or written using a particular system of notation or symbols.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6813976048190be49bb86744b2fb2 |
completed | May 2, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:48 p.m.