Triple
T18880967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukawa meson theory |
E461823
|
entity |
| Predicate | explainsQualitatively |
P264
|
FINISHED |
| Object | saturation of nuclear forces |
—
|
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: saturation of nuclear forces | Statement: [Yukawa meson theory, explainsQualitatively, saturation of nuclear forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explainsQualitatively Context triple: [Yukawa meson theory, explainsQualitatively, saturation of nuclear forces]
-
A.
quantifies
Indicates that one entity expresses or specifies the amount, number, or degree of another entity.
-
B.
describes
chosen
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
C.
aimsToExplain
Indicates that one entity intends to clarify, make understandable, or provide an explanation about another entity, concept, or situation.
-
D.
usedToExplain
Indicates that one entity serves as an explanation or clarification for another entity.
-
E.
clarifiesThat
Indicates that one entity explains or makes another entity more understandable by removing ambiguity or confusion about it.
- 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_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. |
Created at: April 10, 2026, 11:57 a.m.