Triple
T4597673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorentz ether theory |
E100243
|
entity |
| Predicate | sharesMathematicalStructureWith |
P57352
|
FINISHED |
| Object | special relativity |
—
|
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: special relativity | Statement: [Lorentz ether theory, sharesMathematicalStructureWith, special relativity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesMathematicalStructureWith Context triple: [Lorentz ether theory, sharesMathematicalStructureWith, special relativity]
-
A.
sharesComplexWith
Indicates that two entities are components of, or co-residents within, the same larger complex or composite structure.
-
B.
sharesMotifsWith
Indicates that two entities contain or employ similar recurring themes, patterns, or symbolic elements.
-
C.
associatedMatha
Indicates a relationship where one entity is linked or affiliated with a particular matha (monastic or religious institution).
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
sharesElementsWith
Indicates that two entities have one or more elements or components in common.
- 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_69bd43cbc014819098b45f435908f88a |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd59420c108190b5c2c5039e964da5 |
completed | March 20, 2026, 2:27 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56b5f4648190834eafa666d53caa |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:11 p.m.