Triple
T10893620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem King Size |
E257248
|
entity |
| Predicate | relativeLengthToRegular |
P50260
|
FINISHED |
| Object | longer than regular Salem |
—
|
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: longer than regular Salem | Statement: [Salem King Size, relativeLengthToRegular, longer than regular Salem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeLengthToRegular Context triple: [Salem King Size, relativeLengthToRegular, longer than regular Salem]
-
A.
relativeLength
chosen
Indicates a comparative relationship between entities based on how long they are relative to one another.
-
B.
lengthRegime
Indicates a specific range or category of length within which something operates, is measured, or is classified.
-
C.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
-
D.
baseLengthOriginal
Indicates the original or initial length value of a base element before any changes or transformations.
-
E.
proportionalTo
Indicates that one quantity varies in constant ratio to another, so changes in one are directly reflected by proportional changes in the 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75d0089e48190be7a971c2d4f42c2 |
completed | April 9, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.