Triple
T7489935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planck energy |
E176979
|
entity |
| Predicate | usesSymbolForSpeedOfLight |
P76540
|
FINISHED |
| Object | c |
—
|
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: c | Statement: [Planck energy, usesSymbolForSpeedOfLight, c]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSymbolForSpeedOfLight Context triple: [Planck energy, usesSymbolForSpeedOfLight, c]
-
A.
symbolForLorentzFactor
Indicates that one entity is used as the symbolic representation of the Lorentz factor associated with another entity or context.
-
B.
symbolForVelocity
Indicates that one entity is used as the symbolic representation or notation for the concept of velocity of another entity.
-
C.
SIUnitSymbol
Indicates the standardized symbol used to represent a quantity in the International System of Units (SI).
-
D.
symbolForPlanckConstant
Indicates that one entity is the symbolic representation used to denote the Planck constant associated with another entity.
-
E.
isTimeLightTravels
Indicates the duration required for light to travel between specified points or over a specified distance.
- 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_69c69f2583808190bd1a4936c42a5815 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55bdb3481908653b46eafba011d |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f105e320819091db3cdb1f1351f0 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:43 p.m.