Triple
T26244265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomson plum pudding model |
E656398
|
entity |
| Predicate | comparesPositiveChargeTo |
P165848
|
FINISHED |
| Object | pudding |
—
|
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: pudding | Statement: [Thomson plum pudding model, comparesPositiveChargeTo, pudding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comparesPositiveChargeTo Context triple: [Thomson plum pudding model, comparesPositiveChargeTo, pudding]
-
A.
detectsChargeSign
Indicates that one entity determines or identifies the electrical charge polarity (positive or negative) of another entity.
-
B.
orientationOfCharges
Indicates the spatial arrangement or directional alignment between electric charges involved in the relation.
-
C.
isElectricallyNeutral
Indicates that an entity has no net electric charge, with its positive and negative charges balanced.
-
D.
hasChargeConjugation
Indicates that one entity is the charge-conjugated counterpart (particle vs. antiparticle form) of another entity.
-
E.
hasChargePosition
Indicates that one entity occupies or is assigned to a particular official role, office, or position of responsibility within another entity.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a9cb0bc8190bf8a9b319900bad5 |
completed | May 2, 2026, 8:12 p.m. |
Created at: April 26, 2026, 9:04 p.m.