Triple
T15023571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keplerian cosmology |
E378145
|
entity |
| Predicate | containsLaw |
P116428
|
FINISHED |
| Object | Kepler’s first law of planetary motion |
—
|
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: Kepler’s first law of planetary motion | Statement: [Keplerian cosmology, containsLaw, Kepler’s first law of planetary motion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsLaw Context triple: [Keplerian cosmology, containsLaw, Kepler’s first law of planetary motion]
-
A.
containsLawOn
Indicates that one entity (such as a document, code, or regulation) includes or sets forth legal provisions concerning another entity or subject.
-
B.
containsLawType
Indicates that one entity includes or is associated with a specific type or category of law.
-
C.
haveLaw
Indicates that a governing body or jurisdiction possesses, enforces, or is characterized by a particular law or set of laws.
-
D.
appliesLawThrough
Indicates that one entity enforces, implements, or carries out a law or legal rule by means of another entity or mechanism.
-
E.
hasLawTheme
Indicates that something is related to, concerned with, or thematically focused on law or legal matters.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7de117c8190a1b9fa8d1602057e |
completed | April 15, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
| PDg | Predicate description generation | batch_69deb1a88d588190996afa8e5b32b552 |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:56 a.m.