Triple
T10230062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAX IV Laboratory |
E243315
|
entity |
| Predicate | hasAccelerator |
P92883
|
FINISHED |
| Object | linear 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: linear accelerator | Statement: [MAX IV Laboratory, hasAccelerator, linear accelerator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccelerator Context triple: [MAX IV Laboratory, hasAccelerator, linear accelerator]
-
A.
usedAccelerator
Indicates that an entity has applied or made use of an accelerator (such as a device, mechanism, or process) to increase speed, performance, or progress in relation to another entity or activity.
-
B.
parentAccelerator
Indicates that one accelerator entity functions as the parent or higher-level accelerator in relation to another accelerator entity.
-
C.
acceleratedAfter
Indicates that one entity increases its speed or rate of change following, and as a consequence of, another specified event or condition.
-
D.
accelerates
Indicates that one entity causes an increase in the speed or rate of change of another entity or process.
-
E.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d23a9c4c8190abece9e52879c479 |
completed | April 7, 2026, 9:45 a.m. |
Created at: April 6, 2026, 11:19 a.m.