Triple
T27737323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.PropertyAttributes |
E697559
|
entity |
| Predicate | valueOf_Reserved2 |
P165718
|
FINISHED |
| Object | 8192 |
—
|
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: 8192 | Statement: [System.Reflection.PropertyAttributes, valueOf_Reserved2, 8192]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueOf_Reserved2 Context triple: [System.Reflection.PropertyAttributes, valueOf_Reserved2, 8192]
-
A.
isReserved
Indicates that something has been set aside or booked in advance for a particular person, purpose, or time, and is not available for general use.
-
B.
valueOf_SpecialName
chosen
Indicates that one entity represents the specific or special name value assigned to another entity.
-
C.
reservedFor
Indicates that something is set aside or allocated specifically for the use, benefit, or purpose of a particular entity or group.
-
D.
secondSymbolValue
Indicates that the value or quantity associated with the second symbol in a pair or sequence is being specified or referenced.
-
E.
mayBeReservedBy
Indicates that an entity is eligible or allowed to be reserved by another entity, without asserting that the reservation has actually occurred.
- 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_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 3:13 p.m.