Triple
T3451396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Calendar sidebar widget |
E72800
|
entity |
| Predicate | locationInUI |
P15688
|
FINISHED |
| Object | right-hand sidebar of Google Calendar web interface |
—
|
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: right-hand sidebar of Google Calendar web interface | Statement: [Google Calendar sidebar widget, locationInUI, right-hand sidebar of Google Calendar web interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInUI Context triple: [Google Calendar sidebar widget, locationInUI, right-hand sidebar of Google Calendar web interface]
-
A.
uiLocation
chosen
Indicates the on-screen position or placement of a user interface element within a UI layout or display.
-
B.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
C.
locationComponent
Indicates that one entity is a constituent or sub-part of a larger location defined by another entity.
-
D.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
E.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba7465248190947f9096e230e1c4 |
completed | March 8, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.