Triple
T2413229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snap Camera |
E52241
|
entity |
| Predicate | supportsContent |
P13367
|
FINISHED |
| Object | community-created lenses |
—
|
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: community-created lenses | Statement: [Snap Camera, supportsContent, community-created lenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsContent Context triple: [Snap Camera, supportsContent, community-created lenses]
-
A.
supportsCommunityContent
chosen
Indicates that an entity enables, hosts, or facilitates content created and shared by its user or community base.
-
B.
supportsDocument
Indicates that one entity provides compatibility or functionality for handling, processing, or using a particular document or document type.
-
C.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
D.
supportsProduct
Indicates that one entity provides assistance, compatibility, or necessary resources for the operation, use, or maintenance of a specified product.
-
E.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc92a4e1c8190819fa676295ac145 |
completed | March 7, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69abc5a6cbd0819086c0716e266b7ebb |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:41 p.m.