Triple
T7618613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Franck–Hertz experiment |
E172427
|
entity |
| Predicate | typicalVoltageSpacing |
P78144
|
FINISHED |
| Object | approximately 4.9 V |
—
|
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: approximately 4.9 V | Statement: [Franck–Hertz experiment, typicalVoltageSpacing, approximately 4.9 V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVoltageSpacing Context triple: [Franck–Hertz experiment, typicalVoltageSpacing, approximately 4.9 V]
-
A.
typicalVoltagePerCell
Indicates the standard or commonly expected voltage value associated with each individual cell in a multi-cell system or device.
-
B.
gridVoltageLevel
Indicates the electrical voltage level at which a power grid or network segment operates.
-
C.
supplyVoltageType
Indicates the type or category of supply voltage associated with or required by an entity.
-
D.
boreSpacing
Indicates the center-to-center distance between adjacent bores or holes in a component or assembly.
-
E.
usesElectricityVoltage
Indicates that one entity operates using or is characterized by a specified level of electrical voltage supplied by another entity or source.
- 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_69c699506b308190826894dab1d9ea86 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6fe73ff7c8190ab1218d97b37416d |
completed | March 27, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e725a88190b1f05dd224f7f4f2 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6fe7323b0819081664662d2f26937 |
completed | March 27, 2026, 10:02 p.m. |
Created at: March 27, 2026, 3:55 p.m.