Triple
T1463525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International System of Units |
E31565
|
entity |
| Predicate | definesConstant |
P9782
|
FINISHED |
| Object | speed of light in vacuum |
—
|
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: speed of light in vacuum | Statement: [International System of Units, definesConstant, speed of light in vacuum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesConstant Context triple: [International System of Units, definesConstant, speed of light in vacuum]
-
A.
usesConstant
Indicates that one entity makes use of a specific constant value defined or provided by another entity.
-
B.
includesConstant
chosen
Indicates that one entity contains or explicitly references a specific constant value within its definition or structure.
-
C.
constant
Indicates that the relationship or value does not change across different instances, contexts, or over time.
-
D.
defined
Indicates that one entity specifies, explains, or establishes the meaning, scope, or identity of another entity.
-
E.
definedVia
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5b89708819084fb9ba4ff293b8b |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.