Triple
T36978729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot S Series mechanical pencils |
E914764
|
entity |
| Predicate | refillType |
P169020
|
FINISHED |
| Object | mechanical pencil lead |
—
|
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: mechanical pencil lead | Statement: [Pilot S Series mechanical pencils, refillType, mechanical pencil lead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refillType Context triple: [Pilot S Series mechanical pencils, refillType, mechanical pencil lead]
-
A.
refillable
Indicates that an object or container can be filled again with its intended contents after being emptied.
-
B.
refillsAfter
Indicates that one entity replenishes or fills another entity following a specified event, time, or condition.
-
C.
rechargeType
chosen
Indicates the method or mechanism by which something is replenished, refilled, or re-energized.
-
D.
replenishment
Indicates the action or process of refilling or restoring a resource, supply, or quantity to a desired or original level.
-
E.
quillsType
Indicates that one entity has quills of a particular type or classification specified by the other entity.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.