Triple
T15607579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermilab Linac |
E375199
|
entity |
| Predicate | hasVacuumSystem |
P119420
|
FINISHED |
| Object | ultra-high vacuum beamline |
—
|
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: ultra-high vacuum beamline | Statement: [Fermilab Linac, hasVacuumSystem, ultra-high vacuum beamline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVacuumSystem Context triple: [Fermilab Linac, hasVacuumSystem, ultra-high vacuum beamline]
-
A.
hasFillingSystem
Indicates that an entity is equipped with or uses a particular filling system or mechanism.
-
B.
hasVentilationShafts
Indicates that one entity is equipped with or contains ventilation shafts that provide airflow or air passage.
-
C.
ventilationFeature
Indicates that one entity has a structural or functional role related to providing, enabling, or affecting ventilation for another entity.
-
D.
hasSteamVent
Indicates that one entity possesses or contains a steam vent through which steam is released.
-
E.
hasCentralTank
Indicates that an entity possesses or is equipped with a primary central tank as a key component or feature.
- 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_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. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:13 a.m.