Triple
T9004582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live Photos |
E215111
|
entity |
| Predicate | storesComponents |
P63988
|
FINISHED |
| Object | high-resolution still frame |
—
|
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: high-resolution still frame | Statement: [Live Photos, storesComponents, high-resolution still frame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesComponents Context triple: [Live Photos, storesComponents, high-resolution still frame]
-
A.
exchangeListingOfComponents
Indicates that components are listed or registered for trading or exchange between parties or systems.
-
B.
store
chosen
Indicates that one entity keeps or holds another entity in a place or system for future use or access.
-
C.
component3
Indicates that one entity is the third component or sub-part within a larger composite structure or system involving another entity.
-
D.
storesConfigurationFor
Indicates that one entity holds or maintains configuration settings that are used by or apply to another entity.
-
E.
serviceComponentsInclude
Indicates that a service is composed of, or functionally includes, specific component elements.
- 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_69ca83a12d648190b1e4fe11e8a31890 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6959497c8190a748c78504dd2eb6 |
completed | April 1, 2026, 12:39 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:05 p.m.