Triple
T27737319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.PropertyAttributes |
E697559
|
entity |
| Predicate | valueOf_None |
P165405
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [System.Reflection.PropertyAttributes, valueOf_None, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueOf_None Context triple: [System.Reflection.PropertyAttributes, valueOf_None, 0]
-
A.
Null
Indicates that no specific relationship or action is defined or applicable in this context.
-
B.
nullValueSupport
Indicates that the relationship or operation explicitly allows, handles, or preserves null (missing) values for the involved entities or attributes.
-
C.
nullKeySupport
Indicates that the relationship or operation remains valid or supported even when the associated key or identifier is null.
-
D.
emptyValueMeaning
Indicates that a value is intentionally left empty to convey a specific, meaningful state rather than simply missing data.
-
E.
neverRepresentedBy
Indicates that one entity has at no time been represented or acted on behalf of by the other entity.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f659355a208190be2609ffc7a9c427 |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 27, 2026, 3:13 p.m.