Triple
T18880936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukawa meson theory |
E461823
|
entity |
| Predicate | potentialForm |
P133311
|
FINISHED |
| Object | V(r) = -g^2 e^{-μ r} / r |
—
|
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: V(r) = -g^2 e^{-μ r} / r | Statement: [Yukawa meson theory, potentialForm, V(r) = -g^2 e^{-μ r} / r]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: potentialForm
Context triple: [Yukawa meson theory, potentialForm, V(r) = -g^2 e^{-μ r} / r]
-
A.
probabilisticForm
Indicates that the relationship or action is expressed in terms of probabilities or likelihoods rather than as a definite or deterministic form.
-
B.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
C.
mayForm
Indicates that one entity has the potential or permission to be combined or configured to create, constitute, or result in another entity or structure.
-
D.
supportsForm
Indicates that one entity provides compatibility or backing for a particular form, format, or type associated with another entity.
-
E.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside another entity.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d133f08190a482e601c1866662 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e4978813d081908eaf25bb727fc6cf |
completed | April 19, 2026, 8:51 a.m. |
Created at: April 10, 2026, 11:57 a.m.