Triple
T16998850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paper Mate Flair |
E412385
|
entity |
| Predicate | writingLine |
P126107
|
FINISHED |
| Object | medium line width (for medium point variant) |
—
|
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: medium line width (for medium point variant) | Statement: [Paper Mate Flair, writingLine, medium line width (for medium point variant)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingLine Context triple: [Paper Mate Flair, writingLine, medium line width (for medium point variant)]
-
A.
writingForm
Indicates the specific script, notation, or written representation used to express a piece of language or content.
-
B.
formedLine
Indicates that an entity has arranged itself or others into a line or linear formation.
-
C.
written
Indicates that one entity has created or authored a text, document, or written work involving or about another entity.
-
D.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
E.
writingTool
Indicates that one entity serves as a tool or instrument used by another entity for the act of writing.
- F. None of above. chosen
Provenance (4 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_69d886cb581c8190ab05f4b429c9cd85 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d37cd6248190a7202ae754882640 |
completed | April 18, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69e35d552bc08190af17ef7659e094ef |
completed | April 18, 2026, 10:30 a.m. |
| PDg | Predicate description generation | batch_69e378e037c88190935d732e0f10d5d7 |
completed | April 18, 2026, 12:28 p.m. |
Created at: April 10, 2026, 5:32 a.m.