Triple
T26345273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cubic reciprocity law |
E662763
|
entity |
| Predicate | yearFirstProofApprox |
P27180
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [cubic reciprocity law, yearFirstProofApprox, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearFirstProofApprox Context triple: [cubic reciprocity law, yearFirstProofApprox, 19th century]
-
A.
hasFirstProofYear
chosen
Indicates the year in which something was first proven or formally demonstrated to be true.
-
B.
wasFirstProvedBy
Indicates that a particular statement, theorem, or result was originally and for the first time demonstrated or established as true by a specified agent.
-
C.
firstInscriptionYear
Indicates the year in which an entity was first inscribed, recorded, or officially entered into a relevant register or list.
-
D.
estimatedYearOfCreation
Indicates the year in which something is believed or approximated to have been created, rather than a precisely known creation year.
-
E.
initialReleaseApprox
Indicates that an entity’s first release or debut occurred around an estimated or approximate point in time rather than on a precisely known date.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60fa657448190b782aef7e153337f |
completed | May 2, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:41 p.m.