Triple
T14339453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Synchrotron Radiation Laboratory |
E355554
|
entity |
| Predicate | typeOfLightSource |
P73043
|
FINISHED |
| Object | synchrotron light source |
—
|
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: synchrotron light source | Statement: [National Synchrotron Radiation Laboratory, typeOfLightSource, synchrotron light source]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLightSource Context triple: [National Synchrotron Radiation Laboratory, typeOfLightSource, synchrotron light source]
-
A.
lightType
chosen
Indicates the specific category or kind of light associated with an entity or lighting setup.
-
B.
lightSourceFor
Indicates that one entity serves as the source of illumination for another entity.
-
C.
typeOfLampsUsed
Indicates the specific kinds or categories of lamps that are utilized in a given context or system.
-
D.
laterLightSource
Indicates that one light source occurs or is activated after another in time.
-
E.
lightSourceGeneration
Indicates that an entity produces or emits light, serving as a source of illumination for other entities or the environment.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8674c0819091dfbe9c50778c5e |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.