Triple
T17023076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Williams tube |
E412992
|
entity |
| Predicate | writeMethod |
P859
|
FINISHED |
| Object | electron beam positioning |
—
|
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: electron beam positioning | Statement: [Williams tube, writeMethod, electron beam positioning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writeMethod Context triple: [Williams tube, writeMethod, electron beam positioning]
-
A.
writesAs
Indicates that an entity creates written content under a particular name, style, or persona.
-
B.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
C.
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.
-
D.
writesSystem
Indicates that an entity authors or produces a system, such as designing, coding, or otherwise creating it.
-
E.
writerProperty
Indicates that one entity serves as the writer or author associated with another 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d2abbc81908943becf5f539fc6 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.