Triple
T1889550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ELENA ring |
E41837
|
entity |
| Predicate | firstBeamCirculation |
P25622
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [ELENA ring, firstBeamCirculation, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstBeamCirculation Context triple: [ELENA ring, firstBeamCirculation, 2016]
-
A.
firstBeamYear
chosen
Indicates the year in which a beam (such as a particle or radiation beam) was first produced or operated.
-
B.
hasPrimaryCirculation
Indicates that an entity possesses or is associated with a main or principal system, route, or pattern of circulation (such as movement, flow, or distribution).
-
C.
firstCircumscribedBy
Indicates that one entity is the earliest or primary object whose boundary or extent is defined or enclosed by another entity.
-
D.
firstToFeature
Indicates that one entity was the earliest or initial subject to exhibit, include, or present another entity in a given context.
-
E.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
- 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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb142e41881908fc7335673a9dec3 |
completed | March 7, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69abafe61bc48190ac9ead027df930e1 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.