Triple
T30300863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Photos |
E770647
|
entity |
| Predicate | primaryStorageLocation |
P203785
|
FINISHED |
| Object | Photos Library |
—
|
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: Photos Library | Statement: [Apple Photos, primaryStorageLocation, Photos Library]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryStorageLocation Context triple: [Apple Photos, primaryStorageLocation, Photos Library]
-
A.
secondaryStorage
Indicates that an entity serves as a secondary (non-primary) storage location or medium for another entity’s data or resources.
-
B.
storageProperty
Indicates a relationship where an entity has a specific storage-related characteristic, such as capacity, type, or configuration.
-
C.
storageOrgan
Indicates that one entity serves as a storage organ (a specialized structure for storing substances like nutrients or water) for another entity.
-
D.
canBeStoredOn
Indicates that one entity is capable of being placed, kept, or maintained on another entity as a storage location.
-
E.
storedBy
Indicates that one entity is kept, maintained, or held in storage by another entity.
- F. None of above. chosen
Provenance (4 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a020243e2b4819086dbfdcf4372405e |
completed | May 11, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_6a0200f585bc8190b774c54cec409b00 |
completed | May 11, 2026, 4:16 p.m. |
| PDg | Predicate description generation | batch_6a0202432fb08190abf6b83cd7da8deb |
completed | May 11, 2026, 4:22 p.m. |
Created at: April 29, 2026, 7:48 p.m.