Triple
T18815878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | beryllium |
E460131
|
entity |
| Predicate | transparentToXrays |
P40821
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [beryllium, transparentToXrays, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transparentToXrays Context triple: [beryllium, transparentToXrays, true]
-
A.
isTransparentTo
chosen
Indicates that one entity allows another entity (such as light, information, or influence) to pass through or be perceived without obstruction or concealment.
-
B.
transparency
Indicates that an entity’s internal processes, information, or decision-making are openly accessible and understandable to others.
-
C.
usesRadiation
Indicates that an entity employs radiation as a means or component in performing an action, process, or function.
-
D.
visibleUnder
Indicates that one entity can be seen or perceived when another specified condition, context, or covering entity is present or in effect.
-
E.
hasXRaySources
Indicates that an entity possesses or is associated with one or more X-ray emitting sources.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a3e092e081908fc310c70f646e79 |
completed | April 20, 2026, 3:56 a.m. |
| PD | Predicate disambiguation | batch_69e48d1b10ec8190985c6fb5766ff981 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.