Triple
T35889426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Time |
E1037740
|
entity |
| Predicate | centralToTheory |
P195660
|
FINISHED |
| Object | special relativity |
—
|
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: special relativity | Statement: [Time, centralToTheory, special relativity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralToTheory Context triple: [Time, centralToTheory, special relativity]
-
A.
centralConjecture
Indicates that the subject proposition is the main or most important conjecture around which related arguments, results, or discussions are organized.
-
B.
coversTheory
Indicates that one entity includes, addresses, or explains the theoretical concepts associated with another entity.
-
C.
extendsTheoryOf
Indicates that one theory builds upon, broadens, or elaborates the concepts, assumptions, or results of another theory.
-
D.
developsTheory
Indicates that one entity formulates, elaborates, or advances a theoretical framework or explanation concerning another entity.
-
E.
theorized
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fddd373cdc8190be1b12e70e4deb1f |
completed | May 8, 2026, 12:55 p.m. |
| PD | Predicate disambiguation | batch_69fddc6915a88190ad41e379aa3ede13 |
completed | May 8, 2026, 12:51 p.m. |
| PDg | Predicate description generation | batch_69fddd364c1481908794c9d423bdc2d7 |
completed | May 8, 2026, 12:55 p.m. |
Created at: May 3, 2026, 4:06 p.m.