Triple
T36978242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot Hi-Tec-C |
E914753
|
entity |
| Predicate | writingTechnology |
P11833
|
FINISHED |
| Object | needle-point rollerball |
—
|
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: needle-point rollerball | Statement: [Pilot Hi-Tec-C, writingTechnology, needle-point rollerball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writingTechnology Context triple: [Pilot Hi-Tec-C, writingTechnology, needle-point rollerball]
-
A.
writingTool
chosen
Indicates that one entity serves as a tool or instrument used by another entity for the act of writing.
-
B.
writingComponent
Indicates that one entity is a written part or element that contributes to the composition or structure of another entity.
-
C.
fieldOfWriting
Indicates that one entity is the domain, genre, or subject area in which another entity writes or produces written work.
-
D.
writingModel
Indicates that one entity serves as the writing system, script, or notation model used to represent the language or written content of another entity.
-
E.
writingForm
Indicates the specific script, notation, or written representation used to express a piece of language or content.
- 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_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.