Triple
T6369321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernest Walton |
E143306
|
entity |
| Predicate | builtDevice |
P70237
|
FINISHED |
| Object | high-voltage particle accelerator |
—
|
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: high-voltage particle accelerator | Statement: [Ernest Walton, builtDevice, high-voltage particle accelerator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtDevice Context triple: [Ernest Walton, builtDevice, high-voltage particle accelerator]
-
A.
testedDevice
Indicates that one entity has performed a test on, or experimentally evaluated, another entity as a device.
-
B.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
C.
executionDevice
Indicates that an entity serves as the instrument, tool, or device used to carry out or execute a particular action or process.
-
D.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
E.
builtWithout
Indicates that something was constructed or created in the absence of a particular component, material, tool, or condition.
- 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068265a7481908571be7ea4ac11b7 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:33 p.m.