Triple
T5399752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T. D. Lee |
E120742
|
entity |
| Predicate | yearOfParityViolationProposal |
P25813
|
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: [T. D. Lee, yearOfParityViolationProposal, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfParityViolationProposal Context triple: [T. D. Lee, yearOfParityViolationProposal, 1956]
-
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.
leapYearRuleProposedBy
Indicates that a specific rule or method for determining leap years was proposed or formulated by a particular agent or source.
-
C.
originallyProposedFor
Indicates that something was first suggested, designed, or intended to be used for a particular purpose, context, or target.
-
D.
valueParity
Indicates that two compared values share the same parity (both even or both odd), or more generally, how a value’s parity is characterized in a given context.
-
E.
hasFixedParityWith
Indicates that two entities share the same parity property (e.g., both even or both odd) and thus their parity remains consistently matched.
- 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_69bd4637b92c8190b815b6443ae4b323 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.