Triple
T27227558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geiger–Marsden experiment |
E682057
|
entity |
| Predicate | testedModel |
P162264
|
FINISHED |
| Object | Thomson plum pudding model |
—
|
NE NERFINISHED |
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: Thomson plum pudding model | Statement: [Geiger–Marsden experiment, testedModel, Thomson plum pudding model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testedModel Context triple: [Geiger–Marsden experiment, testedModel, Thomson plum pudding model]
-
A.
possibleModel
Indicates that one entity can serve as a potential or candidate model or template for another entity.
-
B.
modelIn
Indicates that one entity serves as a representation or simulation of another entity.
-
C.
model
Indicates that one entity serves as a representation, example, or simulation of another entity or concept.
-
D.
previewedModel
Indicates that one entity has viewed or examined a model in advance, typically before its official use, release, or finalization.
-
E.
testedFor
Indicates that an entity has been examined or analyzed to determine the presence, absence, or level of another specified entity or condition.
- 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_69eefacdad7881908b7bca61c90a1a1e |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6264bcdc08190b0860b3015aac6c6 |
completed | May 2, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69f620e38aec8190bb184edcdbd6da64 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f622a8fe7c819096e8a43db263a423 |
completed | May 2, 2026, 4:13 p.m. |
Created at: April 27, 2026, 9:45 a.m.