Triple
T9770401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | neutrino hypothesis |
E237108
|
entity |
| Predicate | acceptedByCommunity |
P90543
|
FINISHED |
| Object | gradually during 1930s and 1940s |
—
|
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: gradually during 1930s and 1940s | Statement: [neutrino hypothesis, acceptedByCommunity, gradually during 1930s and 1940s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptedByCommunity Context triple: [neutrino hypothesis, acceptedByCommunity, gradually during 1930s and 1940s]
-
A.
usedByCommunity
Indicates that something is utilized or adopted collectively by a particular community.
-
B.
acceptedIn
Indicates that something has been formally received, approved, or admitted into a particular context, group, or system.
-
C.
supportsCommunity
Indicates that one entity provides assistance, resources, or encouragement that benefits a community or group.
-
D.
celebratedByCommunity
Indicates that an event, person, or achievement is honored, recognized, or joyfully acknowledged by a community.
-
E.
acceptedAt
Indicates the time or event at which something (such as a request, submission, or offer) is formally accepted.
- 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_69ca84d831b8819090322686b47887ce |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda0f1dea08190b89bcc192b068c66 |
completed | April 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69cd03d3b68c81909e570401a891b9f2 |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:26 p.m.