Triple
T8436174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun 3/60 |
E199227
|
entity |
| Predicate | caseStyle |
P39478
|
FINISHED |
| Object | pizza-box style desktop |
—
|
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: pizza-box style desktop | Statement: [Sun 3/60, caseStyle, pizza-box style desktop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseStyle Context triple: [Sun 3/60, caseStyle, pizza-box style desktop]
-
A.
letterCase
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
B.
nameStyle
chosen
Indicates how an entity’s name is formatted or stylistically presented (e.g., capitalization, punctuation, or naming convention).
-
C.
casingType
Indicates the specific kind or category of casing associated with or used by an entity.
-
D.
preferredCapitalization
Indicates the specific way a term’s letters should be capitalized when it is written or displayed.
-
E.
codeStandardization
Indicates that multiple pieces of code are being aligned to a common format, style, or set of conventions to ensure consistency.
- 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_69ca8314cd6c8190a6b8c2a1096e18f3 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe30fba4081908bfdef3faf5baceb |
completed | March 31, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69cbd0ec200c8190b0299e2b0b4bdcc2 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:08 p.m.