Triple
T27737403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Reflection.PortableExecutableKinds |
E697561
|
entity |
| Predicate | Preferred32Bit_value |
P107153
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [System.Reflection.PortableExecutableKinds, Preferred32Bit_value, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Preferred32Bit_value Context triple: [System.Reflection.PortableExecutableKinds, Preferred32Bit_value, 16]
-
A.
isPreferredWhen
Indicates that one option, condition, or entity is chosen or favored over others in a particular context or situation.
-
B.
unitPreference
Indicates a relationship where one entity specifies or favors a particular unit of measurement or representation over others.
-
C.
intendedPerformanceMode
Indicates the manner or mode in which an action, process, or performance is meant or designed to be carried out.
-
D.
cpuBits
chosen
Indicates the number of bits used by a CPU’s architecture or word size in the described context.
-
E.
preferredLight
Indicates that one entity favors or is best suited to a particular lighting condition or level of illumination.
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 3:13 p.m.