Triple
T15607580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermilab Linac |
E375199
|
entity |
| Predicate | hasMagnetSystem |
P3957
|
FINISHED |
| Object | focusing and steering magnets |
—
|
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: focusing and steering magnets | Statement: [Fermilab Linac, hasMagnetSystem, focusing and steering magnets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagnetSystem Context triple: [Fermilab Linac, hasMagnetSystem, focusing and steering magnets]
-
A.
hasMagnetStatus
Indicates that an entity possesses a specific magnet-related state or designation within a given context.
-
B.
usesMagnetType
chosen
Indicates that one entity employs or operates with a specific type of magnet in its function or configuration.
-
C.
hasMagneticMoment
Indicates that an entity possesses a magnetic moment, characterizing the strength and orientation of its magnetism.
-
D.
hasMagneticHeading
Indicates the directional orientation of an entity relative to magnetic north, typically expressed as a magnetic compass bearing.
-
E.
hasMagnetosphere
Indicates that an astronomical body possesses a magnetic field strong enough to create a surrounding magnetosphere.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7ec08c8190b3842cf3043aea27 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:13 a.m.