Triple
T11960687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nokia 3.2 |
E284660
|
entity |
| Predicate | displayNotchType |
P102499
|
FINISHED |
| Object | waterdrop notch |
—
|
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: waterdrop notch | Statement: [Nokia 3.2, displayNotchType, waterdrop notch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayNotchType Context triple: [Nokia 3.2, displayNotchType, waterdrop notch]
-
A.
screenCurvature
Indicates that one entity has a specific degree or type of curvature in its screen surface relative to another entity or a defined standard.
-
B.
displayConfiguration
Indicates a relationship where one entity defines or presents the arrangement, layout, or settings used to visually display another entity.
-
C.
displayChip
Indicates that one entity presents or renders another entity as a chip-style visual element in a user interface.
-
D.
touchscreenType
Indicates the specific kind or technology of touchscreen associated with an entity.
-
E.
displayMode
Indicates how content or information is visually presented or arranged to the user.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9036941948190b150369094551731 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8dd0ba0f88190b7d5e358c27ca184 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 8, 2026, 9:45 p.m.