Triple
T3316942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LINAC3 |
E69703
|
entity |
| Predicate | physicsDiscipline |
P5484
|
FINISHED |
| Object | accelerator physics |
—
|
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: accelerator physics | Statement: [LINAC3, physicsDiscipline, accelerator physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physicsDiscipline Context triple: [LINAC3, physicsDiscipline, accelerator physics]
-
A.
physicalBasis
Indicates that one entity serves as the underlying physical foundation, mechanism, or substrate that gives rise to or supports the properties, behavior, or existence of another entity.
-
B.
subDisciplineOf
chosen
Indicates that one discipline is a more specialized or narrower field within another, broader discipline.
-
C.
dimensionOfStudy
Indicates the specific field, aspect, or perspective that characterizes or structures a particular study or research activity.
-
D.
secondScience
Indicates that the subject is the second entity in a sequence or ranking specifically within a scientific context or domain.
-
E.
featuredDiscipline
Indicates that one discipline is highlighted or given special prominence in relation to another entity or context.
- 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_69ad85a0bb048190a5458d2738012d61 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb11230b881908f5b554323729cc5 |
completed | March 8, 2026, 5:25 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.