Triple
T15131791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Active Edge |
E361437
|
entity |
| Predicate | inputLocation |
P117440
|
FINISHED |
| Object | sides of the phone 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: sides of the phone frame | Statement: [Active Edge, inputLocation, sides of the phone frame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputLocation Context triple: [Active Edge, inputLocation, sides of the phone frame]
-
A.
uiLocation
Indicates the on-screen position or placement of a user interface element within a UI layout or display.
-
B.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
-
C.
leftLocation
Indicates that an entity has departed from or moved away from a specified location.
-
D.
mainLocation
Indicates that one entity serves as the primary or central location associated with another entity.
-
E.
firstLocation
Indicates the initial or primary place where an entity is situated, originates, or where an event or relationship begins.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:06 a.m.