Triple
T18203404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aharonov–Bohm effect |
E435846
|
entity |
| Predicate | hasYearProposed |
P25813
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [Aharonov–Bohm effect, hasYearProposed, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYearProposed Context triple: [Aharonov–Bohm effect, hasYearProposed, 1959]
-
A.
proposedInYear
chosen
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
-
B.
hasProposed
Indicates that one entity has formally suggested or put forward something (such as an idea, plan, or offer) to another entity for consideration or acceptance.
-
C.
originallyProposedFor
Indicates that something was first suggested, designed, or intended to be used for a particular purpose, context, or target.
-
D.
hasProposal
Indicates that an entity possesses, is associated with, or is the subject of a specific proposal.
-
E.
hasFirstMajorProposalDate
Indicates the date on which an entity’s first major proposal was formally made or recorded.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e221bbbc819088a7559a46b7d4e7 |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.