Triple
T8832118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | antiprotonic helium |
E210169
|
entity |
| Predicate | hasBindingMechanism |
P8166
|
FINISHED |
| Object | Coulomb interaction |
—
|
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: Coulomb interaction | Statement: [antiprotonic helium, hasBindingMechanism, Coulomb interaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBindingMechanism Context triple: [antiprotonic helium, hasBindingMechanism, Coulomb interaction]
-
A.
hasMechanism
chosen
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
B.
hasBindingEnergy
Indicates that one entity possesses or is characterized by a specific amount of binding energy associated with its formation or stability.
-
C.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
-
D.
hasBondType
Indicates the specific kind of bond or connection that exists between two related entities.
-
E.
isNotBindingOn
Indicates that an agreement, rule, or obligation does not have legal or enforceable effect on the referenced entity.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc605005788190a4df1fe317f3056a |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:47 p.m.