Triple
T2175062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storage Standard |
E48507
|
entity |
| Predicate | definesAPIFor |
P31856
|
FINISHED |
| Object | client-side data storage |
—
|
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: client-side data storage | Statement: [Storage Standard, definesAPIFor, client-side data storage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesAPIFor Context triple: [Storage Standard, definesAPIFor, client-side data storage]
-
A.
hasAPIs
chosen
Indicates that one entity provides or exposes application programming interfaces (APIs) that can be used or accessed by another entity.
-
B.
definedOn
Indicates that something (such as a function, rule, or structure) is specified to apply or be valid over a particular domain, set, or context.
-
C.
areDefinedIn
Indicates that the referenced entities are specified, described, or formally established within a particular source, context, or scope.
-
D.
definesCommand
Indicates that one entity specifies or establishes a command that another entity can execute or obey.
-
E.
definedVia
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc1559ff481908efe3f214b2570dc |
completed | March 7, 2026, 6:10 a.m. |
| PD | Predicate disambiguation | batch_69abbd9efc1c81909a65044a1ffc9038 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.