Triple
T37456137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humble Store |
E930803
|
entity |
| Predicate | loginSystem |
P185829
|
FINISHED |
| Object | Humble account |
—
|
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: Humble account | Statement: [Humble Store, loginSystem, Humble account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loginSystem Context triple: [Humble Store, loginSystem, Humble account]
-
A.
userSystem
Indicates a relationship where a user interacts with, accesses, or is associated with a particular system.
-
B.
authenticationSystem
Indicates that an entity functions as or is associated with a system responsible for verifying identities and controlling access.
-
C.
loginComponent
chosen
Indicates a relationship where a component is responsible for handling or facilitating a user's login process.
-
D.
loginOptions
Indicates the available methods or configurations a user can choose from when signing into a system or application.
-
E.
registrationSystem
Indicates a system or process responsible for recording, managing, and maintaining registrations or enrollments for entities.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.