Triple
T5767252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherenkov detector |
E127244
|
entity |
| Predicate | infers |
P4466
|
FINISHED |
| Object | particle velocity from Cherenkov angle |
—
|
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: particle velocity from Cherenkov angle | Statement: [Cherenkov detector, infers, particle velocity from Cherenkov angle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infers Context triple: [Cherenkov detector, infers, particle velocity from Cherenkov angle]
-
A.
usedToInfer
chosen
Indicates that one entity serves as a basis or source from which another entity is logically derived or concluded.
-
B.
implies
Indicates that the truth of one statement guarantees or leads logically to the truth of another statement.
-
C.
anticipates
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
-
D.
assumes
Indicates that one entity takes on, accepts, or presumes a role, responsibility, state, or fact regarding another entity or situation.
-
E.
inducts
Indicates formally bringing someone into a group, organization, office, or honor by an official or ceremonial process.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021ce8d3c81909b332cb1c33a61ad |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:49 p.m.