Triple
T18880961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yukawa meson theory |
E461823
|
entity |
| Predicate | potentialType |
P58576
|
FINISHED |
| Object | central potential |
—
|
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: central potential | Statement: [Yukawa meson theory, potentialType, central potential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: potentialType Context triple: [Yukawa meson theory, potentialType, central potential]
-
A.
potentialBasing
Indicates a relationship where one entity could serve as the base, foundation, or supporting location for another, but this basing has not yet been realized or confirmed.
-
B.
powersType
Indicates that one entity has a specific type or category of power or ability in relation to another entity.
-
C.
exportPotential
Indicates the extent to which something is suitable or likely to be successfully exported to other markets or locations.
-
D.
hasPotential
chosen
Indicates that an entity possesses the capacity or possibility to develop, achieve, or exhibit a particular state, quality, or outcome in the future.
-
E.
permitType
Indicates the specific category or kind of permit associated with an entity or activity.
- 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.