Triple
T36796905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LinkedIn Stories |
E909206
|
entity |
| Predicate | interfaceFormat |
P130
|
FINISHED |
| Object | vertical, full-screen format |
—
|
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: vertical, full-screen format | Statement: [LinkedIn Stories, interfaceFormat, vertical, full-screen format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interfaceFormat Context triple: [LinkedIn Stories, interfaceFormat, vertical, full-screen format]
-
A.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
B.
includeFormat
Indicates that one entity contains or specifies the format or representation type of another entity.
-
C.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
-
D.
featuresFormat
Indicates that something (such as a product, service, or medium) is presented, delivered, or made available in a particular format or configuration.
-
E.
openFormat
Indicates that an entity is presented or made available in a format that is open, accessible, and not restricted by proprietary constraints.
- 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_69f76e7b98888190899b6478a82ad6ae |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69feafa1ba0081909013800b85a9f613 |
completed | May 9, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69feae58d62c81909d031f3df8992883 |
completed | May 9, 2026, 3:47 a.m. |
Created at: May 3, 2026, 4:12 p.m.