Triple
T32043909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kinematic Relativity |
E818286
|
entity |
| Predicate | attemptsToExplain |
P5130
|
FINISHED |
| Object | Hubble–Lemaître law |
—
|
NE NERFINISHED |
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: Hubble–Lemaître law | Statement: [Kinematic Relativity, attemptsToExplain, Hubble–Lemaître law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptsToExplain Context triple: [Kinematic Relativity, attemptsToExplain, Hubble–Lemaître law]
-
A.
aimsToExplain
chosen
Indicates that one entity intends to clarify, make understandable, or provide an explanation about another entity, concept, or situation.
-
B.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
-
C.
claimsToExplain
Indicates that one entity asserts it can provide a clarification, account, or understanding of another entity or phenomenon.
-
D.
refusedToExplain
Indicates that an entity declined or failed to provide an explanation about something to another entity or audience.
-
E.
laterExplained
Indicates that an earlier event, statement, or situation is clarified or made understandable by information provided at a subsequent time.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b967d5308190bbb66d0a8dd52612 |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:19 a.m.