Triple
T28264009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google+ |
E712652
|
entity |
| Predicate | loginSystemRole |
P12085
|
FINISHED |
| Object | Google-wide identity layer |
—
|
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: Google-wide identity layer | Statement: [Google+, loginSystemRole, Google-wide identity layer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loginSystemRole Context triple: [Google+, loginSystemRole, Google-wide identity layer]
-
A.
ClientRole
Indicates that an entity participates in a relationship or interaction specifically in the capacity of a client.
-
B.
loginScope
Indicates the specific permissions, access range, or contextual boundaries under which a user or system is authenticated during a login session.
-
C.
userSystem
Indicates a relationship where a user interacts with, accesses, or is associated with a particular system.
-
D.
systemRole
chosen
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
E.
testRole
Indicates that an entity is assigned or associated with a specific role used for testing or validation purposes.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6441c2ed081909128d8fe21b14fa4 |
completed | May 2, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:13 p.m.