Triple
T27559622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surface Pro Type Cover |
E695737
|
entity |
| Predicate | layoutOption |
P51177
|
FINISHED |
| Object | US English layout |
—
|
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: US English layout | Statement: [Surface Pro Type Cover, layoutOption, US English layout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutOption Context triple: [Surface Pro Type Cover, layoutOption, US English layout]
-
A.
layoutOptions
chosen
Indicates how elements are arranged or positioned relative to each other within a given space or structure.
-
B.
layoutSupport
Indicates that one entity provides or enables structural or spatial arrangement capabilities for another entity.
-
C.
layoutShape
Indicates a spatial or structural arrangement relationship where one entity defines or influences the geometric shape or configuration of another.
-
D.
layoutRole
Indicates how an entity functions or is positioned within a larger structural or spatial arrangement.
-
E.
layoutDetail
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62fb839fc81909bdfc34aac33dcf6 |
completed | May 2, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69f62c1921008190a62675a31f66a875 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:38 p.m.