Triple
T3921401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fermi constant |
E88966
|
entity |
| Predicate | determinedFrom |
P909
|
FINISHED |
| Object | muon lifetime measurements |
—
|
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: muon lifetime measurements | Statement: [Fermi constant, determinedFrom, muon lifetime measurements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: determinedFrom Context triple: [Fermi constant, determinedFrom, muon lifetime measurements]
-
A.
determinedBy
Indicates that one entity’s state, value, or outcome is decided, controlled, or fully specified by another entity.
-
B.
determined
Indicates that an entity has firmly decided on a course of action or conclusion, typically after consideration or effort.
-
C.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
D.
declaredFrom
Indicates that one entity is formally announced, stated, or proclaimed by another as its source or origin.
-
E.
derivedBy
Indicates that one entity is obtained, produced, or inferred from another through some transformation, process, or reasoning.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.