Triple
T30773960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huawei P50 Pro |
E783607
|
entity |
| Predicate | displayCurvature |
P43676
|
FINISHED |
| Object | curved edges |
—
|
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: curved edges | Statement: [Huawei P50 Pro, displayCurvature, curved edges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: displayCurvature Context triple: [Huawei P50 Pro, displayCurvature, curved edges]
-
A.
usesCurvature
Indicates that one entity applies or relies on the curvature property or measure of another entity in its operation, definition, or analysis.
-
B.
curvatureCondition
Indicates that a specified geometric object or path satisfies a particular constraint or requirement on its curvature.
-
C.
hasCurvatureInvariant
Indicates that one entity possesses a specific curvature-related invariant property or value associated with its geometric or mathematical structure.
-
D.
hasCurvatureBehavior
Indicates how the curvature of an object or path behaves or changes under specified conditions or over a given domain.
-
E.
screenCurvature
chosen
Indicates that one entity has a specific degree or type of curvature in its screen surface relative to another entity or a defined standard.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68fc421dc8190862169489455a035 |
completed | May 2, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:40 p.m.