Triple
T27733463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Environment |
E697480
|
entity |
| Predicate | hasEnum |
P164522
|
FINISHED |
| Object | Environment.SpecialFolder |
—
|
NE NERFINISHED |
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: Environment.SpecialFolder | Statement: [System.Environment, hasEnum, Environment.SpecialFolder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnum Context triple: [System.Environment, hasEnum, Environment.SpecialFolder]
-
A.
isEnum
Indicates that something is classified as an enumeration type, representing a fixed set of discrete, named values.
-
B.
usesEnum
chosen
Indicates that one entity employs or references an enumeration type defined by another entity.
-
C.
isFlagsEnum
Indicates that an enumeration type is intended to be used as a bit field, where its values can be combined using bitwise operations to represent multiple flags simultaneously.
-
D.
hasDifferentEnumerationsIn
Indicates that the same concept or item is represented with differing sets of enumeration values across the specified contexts or systems.
-
E.
hasCol
Indicates that one entity possesses, contains, or is associated with a particular color.
- 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_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 3:12 p.m.