Triple
T4053667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukawa potential |
E84642
|
entity |
| Predicate | hasDimensionality |
P53031
|
FINISHED |
| Object | energy |
—
|
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: energy | Statement: [Yukawa potential, hasDimensionality, energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDimensionality Context triple: [Yukawa potential, hasDimensionality, energy]
-
A.
hasDimension
Indicates that an entity possesses a specific measurable extent or size along one or more axes (e.g., length, width, height).
-
B.
hasDimensionParameter
Indicates that an entity is associated with a specific dimensional parameter (such as size, length, width, or height) that characterizes its measurable extent.
-
C.
dimensionCount
Indicates the number of distinct dimensions or axes associated with an entity or data structure.
-
D.
includesDimension
Indicates that one entity encompasses or contains a particular dimension or measurable aspect as part of its definition or structure.
-
E.
dimensionEquals
Indicates that two entities have exactly the same dimensional properties or measurements.
- 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_69aed933bec881909edfa28ebb69c634 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef90249e4819095e9e043bc4aa9a6 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef9fcb31c819098d5287b6fc84f4e |
completed | March 9, 2026, 4:49 p.m. |
Created at: March 9, 2026, 3:37 p.m.