Triple
T29408971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ubuntu 15.04 |
E745842
|
entity |
| Predicate | defaultLoginManager |
P180629
|
FINISHED |
| Object | LightDM |
—
|
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: LightDM | Statement: [Ubuntu 15.04, defaultLoginManager, LightDM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultLoginManager Context triple: [Ubuntu 15.04, defaultLoginManager, LightDM]
-
A.
defaultLoginTimeout
Indicates the standard amount of time a login session or login attempt is allowed to remain active before it automatically expires or times out.
-
B.
anonymousLoginUsername
Indicates that a username is used specifically for logging in anonymously, without revealing the user's real identity.
-
C.
logonName
Indicates the login identifier or username associated with an entity for authentication or access purposes.
-
D.
userSystem
Indicates a relationship where a user interacts with, accesses, or is associated with a particular system.
-
E.
loginScope
Indicates the specific permissions, access range, or contextual boundaries under which a user or system is authenticated during a login session.
- F. None of above. chosen
Provenance (4 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 28, 2026, 2:55 p.m.