Triple
T21989410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherenkov radiation |
E543043
|
entity |
| Predicate | doesNotViolate |
P4300
|
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: [Cherenkov radiation, doesNotViolate, special relativity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotViolate Context triple: [Cherenkov radiation, doesNotViolate, special relativity]
-
A.
doesNotImpose
Indicates that one entity refrains from placing requirements, restrictions, or burdens upon another entity.
-
B.
doesNot
chosen
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
C.
doesNotConstitute
Indicates that one thing is insufficient or inadequate to qualify as, amount to, or be considered as another thing.
-
D.
doesNotBan
Indicates that one entity allows or permits another entity or action by explicitly not prohibiting it.
-
E.
doesNotAbolish
Indicates that one entity, action, or law does not eliminate, revoke, or put an end to another.
- 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_69e0c48136b081908831fa907cc02e18 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1270cb67c81909a3aa2dc61c1894f |
completed | April 28, 2026, 9:30 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:05 p.m.