Triple
T14453869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samsung Galaxy Z Fold |
E358403
|
entity |
| Predicate | unfoldedDisplayType |
P5731
|
FINISHED |
| Object | tablet-sized display |
—
|
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: tablet-sized display | Statement: [Samsung Galaxy Z Fold, unfoldedDisplayType, tablet-sized display]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unfoldedDisplayType Context triple: [Samsung Galaxy Z Fold, unfoldedDisplayType, tablet-sized display]
-
A.
displayType
Indicates the manner or format in which something is presented, shown, or rendered.
-
B.
displayedWith
Indicates that one entity is shown or presented together alongside another entity in the same context or view.
-
C.
dataTypeDisplayed
Indicates that a particular data type is currently being shown or rendered in a given context or interface.
-
D.
hasDisplayType
chosen
Indicates the type or category of display associated with an entity, such as the format, mode, or presentation style used to show its content.
-
E.
foldingType
Indicates the specific manner or configuration in which something is folded or arranged into a folded form.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a8bf088190abf5fd4f646b8c62 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.