Triple
T7188614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | kelvin |
E167630
|
entity |
| Predicate | definitionMethod |
P27208
|
FINISHED |
| Object | fixed numerical value of Boltzmann constant |
—
|
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: fixed numerical value of Boltzmann constant | Statement: [kelvin, definitionMethod, fixed numerical value of Boltzmann constant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definitionMethod Context triple: [kelvin, definitionMethod, fixed numerical value of Boltzmann constant]
-
A.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
B.
definedVia
chosen
Indicates that one entity is specified, characterized, or given its meaning by reference to another entity or construct.
-
C.
method
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
D.
definesType
Indicates that one entity specifies or establishes the type or classification of another entity.
-
E.
methodOfRule
Indicates the specific method, procedure, or approach by which a rule is applied, implemented, or enforced.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8e3d9188190ba2792098d76fb86 |
completed | March 27, 2026, 8:30 p.m. |
| PD | Predicate disambiguation | batch_69c6e752385c819096fbab55566ee2a8 |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:50 p.m.