Triple
T28583792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | progman.exe |
E723439
|
entity |
| Predicate | visibleName |
P163278
|
FINISHED |
| Object | Program Manager |
—
|
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: Program Manager | Statement: [progman.exe, visibleName, Program Manager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleName Context triple: [progman.exe, visibleName, Program Manager]
-
A.
displayName
chosen
Indicates the human-readable name or label that is shown to users when presenting an entity.
-
B.
visibleUnder
Indicates that one entity can be seen or perceived when another specified condition, context, or covering entity is present or in effect.
-
C.
visibleAt
Indicates that one entity can be seen or perceived from a specific location, viewpoint, or context at a given time.
-
D.
visibleByDefault
Indicates that something is initially shown or accessible without requiring any additional action or configuration to make it visible.
-
E.
veilName
Indicates that an entity is associated with or identified by a particular veil-related name or alias.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650ce24ec8190aa08f8477fa41ce0 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 4:16 a.m.