Triple
T23902563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakata model of hadrons |
E601092
|
entity |
| Predicate | approximateProposalYear |
P154022
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [Sakata model of hadrons, approximateProposalYear, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateProposalYear Context triple: [Sakata model of hadrons, approximateProposalYear, 1956]
-
A.
approximateDesignYear
Indicates the estimated or inferred year in which something was designed, rather than a precisely known design year.
-
B.
retitleApproxYear
Indicates that an entity was retitled or renamed around an approximate year, rather than at a precisely known date.
-
C.
approximateYearOfCompletion
Indicates the estimated calendar year in which something was completed, rather than an exact or confirmed year.
-
D.
releaseApproximateYear
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
E.
approximateYearWritten
Indicates the estimated calendar year in which something was written, when the exact year is not known.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cddf46948190b8625811725fe41d |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 8:26 p.m.