Triple
T5412512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copernicus (lunar crater) |
E121044
|
entity |
| Predicate | eponymApprovalYear |
P63291
|
FINISHED |
| Object | 1935 |
—
|
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: 1935 | Statement: [Copernicus (lunar crater), eponymApprovalYear, 1935]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eponymApprovalYear Context triple: [Copernicus (lunar crater), eponymApprovalYear, 1935]
-
A.
eponymFor
Indicates that one entity gives its name to another entity, which is then named after it.
-
B.
regulatoryApprovalYear
Indicates the calendar year in which an official regulatory body granted approval for the referenced item, action, or entity.
-
C.
IUPACApprovalYear
Indicates the year in which a substance or nomenclature was officially approved by IUPAC.
-
D.
proposedInYear
Indicates that something, such as a plan, idea, or piece of legislation, was formally put forward or suggested in a specific calendar year.
-
E.
originYear
Indicates the year in which something first originated, was created, or began.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bb3c0c81908711784bc865ff03 |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd865702ec8190831bde2c2a331f28 |
completed | March 20, 2026, 5:39 p.m. |
Created at: March 20, 2026, 2:05 p.m.