Triple
T36543855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RealMe |
E901089
|
entity |
| Predicate | loginComponent |
P185829
|
FINISHED |
| Object | RealMe login |
—
|
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: RealMe login | Statement: [RealMe, loginComponent, RealMe login]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loginComponent Context triple: [RealMe, loginComponent, RealMe login]
-
A.
loginOptions
Indicates the available methods or configurations a user can choose from when signing into a system or application.
-
B.
loginScope
Indicates the specific permissions, access range, or contextual boundaries under which a user or system is authenticated during a login session.
-
C.
anonymousLoginUsername
Indicates that a username is used specifically for logging in anonymously, without revealing the user's real identity.
-
D.
logonName
Indicates the login identifier or username associated with an entity for authentication or access purposes.
-
E.
authenticationSystem
Indicates that an entity functions as or is associated with a system responsible for verifying identities and controlling access.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.