Triple
T33435008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Screen Orientation API |
E856219
|
entity |
| Predicate | orientationLockExample |
P9934
|
FINISHED |
| Object | portrait |
—
|
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: portrait | Statement: [Screen Orientation API, orientationLockExample, portrait]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientationLockExample Context triple: [Screen Orientation API, orientationLockExample, portrait]
-
A.
orientationException
Indicates an exception or deviation from the normal or expected orientation relationship between entities.
-
B.
sessionOrientation
chosen
Indicates the directional or spatial alignment relationship established between entities within a session or interaction context.
-
C.
performanceOrientation
Indicates a relationship where an entity is characterized by a focus on achieving high performance, results, or measurable outcomes in its activities or behavior.
-
D.
portraitStyle
Indicates the artistic style or manner in which a portrait is created or depicted.
-
E.
locationOrientation
Indicates how one entity is spatially oriented or positioned relative to a specific location or reference point.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:36 a.m.