Triple
T23837460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rindler coordinates |
E590891
|
entity |
| Predicate | generatorOfTimeTranslations |
P153821
|
FINISHED |
| Object | Lorentz boost Killing vector |
—
|
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: Lorentz boost Killing vector | Statement: [Rindler coordinates, generatorOfTimeTranslations, Lorentz boost Killing vector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generatorOfTimeTranslations Context triple: [Rindler coordinates, generatorOfTimeTranslations, Lorentz boost Killing vector]
-
A.
eraOfTranslation
Indicates the historical period or era during which a given work was translated.
-
B.
dateOfTranslation
Indicates the specific date on which a translation of a work or text was completed or officially produced.
-
C.
translationYear
Indicates the year in which something (typically a work or text) was translated into another language.
-
D.
timeDescribedAs
Indicates that a specific time or temporal interval is characterized, labeled, or expressed using a particular description or representation.
-
E.
centuryOfTranslation
Indicates the century during which a translation of a work or text was produced.
- 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_69e25d1de32c8190a907afe9c3d6cd6d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c883c7108190b3cce6fec0b8609a |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8:07 p.m.