Triple
T31403380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ole Rømer |
E801058
|
entity |
| Predicate | estimatedSpeedOfLight |
P88274
|
FINISHED |
| Object | approximately 220,000 km/s |
—
|
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: approximately 220,000 km/s | Statement: [Ole Rømer, estimatedSpeedOfLight, approximately 220,000 km/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedSpeedOfLight Context triple: [Ole Rømer, estimatedSpeedOfLight, approximately 220,000 km/s]
-
A.
speedOfLightInVacuumApprox
chosen
Indicates the approximate numerical value of the speed at which light propagates through a perfect vacuum.
-
B.
usesSymbolForSpeedOfLight
Indicates that an entity employs a particular symbol to represent the speed of light in some context or notation.
-
C.
constantInVacuum
Indicates that the related quantity remains unchanged when measured in a vacuum, independent of external conditions or context.
-
D.
meteorVelocity
Indicates the speed and direction at which a meteor is moving through space or an atmosphere.
-
E.
isTimeLightTravels
Indicates the duration required for light to travel between specified points or over a specified distance.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 9:20 p.m.