Triple
T1403837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler’s laws of planetary motion |
E31644
|
entity |
| Predicate | furtherPublicationYear |
P27611
|
FINISHED |
| Object | 1619 |
—
|
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: 1619 | Statement: [Kepler’s laws of planetary motion, furtherPublicationYear, 1619]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: furtherPublicationYear Context triple: [Kepler’s laws of planetary motion, furtherPublicationYear, 1619]
-
A.
publicationYear
Indicates the specific calendar year in which a work was formally published or released.
-
B.
subsequentPublication
Indicates that one publication was released after another in time, making it a later or follow-up work relative to the first.
-
C.
laterCollectionPublicationYear
Indicates that the referenced collection was published in a year later than the year associated with the compared collection or work.
-
D.
frontiersReferenceYear
Indicates the specific year to which a given Frontiers reference or citation pertains.
-
E.
publicationPeriod
Indicates the span of time during which something is published, active in publication, or valid as a published work.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3a0330c8190b22452d29c79fcf4 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c11067b48190bca6ef3ac1475c20 |
completed | March 1, 2026, 10:43 p.m. |
Created at: March 1, 2026, 7:59 p.m.