Triple
T4269721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Made by Google 2023 event |
E96910
|
entity |
| Predicate | emphasizesFeatureCategory |
P7153
|
FINISHED |
| Object | mobile photography |
—
|
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: mobile photography | Statement: [Made by Google 2023 event, emphasizesFeatureCategory, mobile photography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesFeatureCategory Context triple: [Made by Google 2023 event, emphasizesFeatureCategory, mobile photography]
-
A.
categoryFocus
Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
-
B.
keyFeature
chosen
Indicates that something is a primary, distinguishing, or most important feature of an entity.
-
C.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
D.
culturalEmphasis
Indicates that a culture, group, or context places particular importance or priority on a specific value, practice, or domain.
-
E.
skillEmphasis
Indicates that a particular skill is given special focus, priority, or importance within a context such as a role, task, or curriculum.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ffa30c08190913622ffec47d33d |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.