Triple
T34561243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | This Perfect Day |
E887345
|
entity |
| Predicate | governingComputerName |
P55846
|
FINISHED |
| Object | UniComp |
—
|
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: UniComp | Statement: [This Perfect Day, governingComputerName, UniComp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingComputerName Context triple: [This Perfect Day, governingComputerName, UniComp]
-
A.
nicknameOfComputer
Indicates that one term is an informal or familiar nickname used to refer to a particular computer.
-
B.
systemName
chosen
Indicates that an entity has a specific system-level name or identifier assigned to it.
-
C.
hostFullName
Indicates that one entity is the complete personal name (including given and family names, and possibly middle names or titles) of the host associated with another entity.
-
D.
logonName
Indicates the login identifier or username associated with an entity for authentication or access purposes.
-
E.
computingCenter
Indicates that an entity functions as or is associated with a computing center, i.e., a facility or unit where computing resources and services are provided or managed.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a013e23698c81909a32d371b6f158d0 |
completed | May 11, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_6a013db04b108190985897aa6e95b4ec |
completed | May 11, 2026, 2:23 a.m. |
Created at: May 1, 2026, 2:02 a.m.