Triple
T9937927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Møller scattering |
E194002
|
entity |
| Predicate | hasInitialState |
P91248
|
FINISHED |
| Object | two electrons |
—
|
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: two electrons | Statement: [Møller scattering, hasInitialState, two electrons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInitialState Context triple: [Møller scattering, hasInitialState, two electrons]
-
A.
hasInitial
Indicates that one entity possesses or is associated with the first letter or starting character of another entity’s name or value.
-
B.
hasCoreState
Indicates that an entity possesses or is associated with a fundamental or primary state that defines its core condition or behavior.
-
C.
hasFirstTerm
Indicates that an entity is associated with a specific first term in an ordered sequence, period, or series.
-
D.
hasInitiation
Indicates that one entity initiates, starts, or triggers an action, process, or relationship involving another entity.
-
E.
hasFirstHolder
Indicates that an entity is associated with the earliest or original holder (e.g., owner, position-bearer, or title-holder) of something.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5e64760819094f599f158d32f33 |
completed | April 2, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd358386f48190833c862b5b8c04b2 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:44 p.m.