Triple
T27636580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MatSnackBar |
E696486
|
entity |
| Predicate | defaultHorizontalPosition |
P39553
|
FINISHED |
| Object | center |
—
|
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: center | Statement: [MatSnackBar, defaultHorizontalPosition, center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultHorizontalPosition Context triple: [MatSnackBar, defaultHorizontalPosition, center]
-
A.
defaultPosition
Indicates the standard or initial spatial arrangement or pose that an entity assumes in the absence of other specified positions.
-
B.
horizontalAxis
chosen
Indicates that one entity serves as the horizontal reference line or direction along which another entity is oriented, measured, or arranged.
-
C.
canonicalPlacement
Indicates the standard or preferred position or arrangement of one entity relative to another within a defined structure or system.
-
D.
textAlignment
Indicates how text is positioned or aligned relative to a reference frame, such as margins, columns, or other layout boundaries.
-
E.
verticalBandPosition
Indicates the relative vertical placement or ordering of a band or stripe within a larger layout or structure.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:24 p.m.