Triple
T8608647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sugar on a Stick |
E203865
|
entity |
| Predicate | userDataStoredOn |
P1596
|
FINISHED |
| Object | USB device |
—
|
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: USB device | Statement: [Sugar on a Stick, userDataStoredOn, USB device]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userDataStoredOn Context triple: [Sugar on a Stick, userDataStoredOn, USB device]
-
A.
policyStoredIn
Indicates that a policy is kept or maintained within a particular storage location or system.
-
B.
dataPolicy
Indicates that one entity defines or governs how data related to another entity is collected, used, stored, or shared.
-
C.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
-
D.
userDataDeletion
Indicates that a user's stored data is removed or erased from a system or service.
-
E.
dataStorage
chosen
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ed77588190a872d22d9d1f7429 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc454eb2908190acf0e4336bc67e7b |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:25 p.m.