Triple
T2321413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tau neutrino |
E51187
|
entity |
| Predicate | isWeaklyInteracting |
P38061
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [tau neutrino, isWeaklyInteracting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWeaklyInteracting Context triple: [tau neutrino, isWeaklyInteracting, true]
-
A.
hasWeakIsospin
Indicates that an entity possesses a specified value of weak isospin, representing its charge under the weak nuclear interaction.
-
B.
hasWeakHypercharge
Indicates that an entity possesses a specified value of weak hypercharge, the U(1) gauge charge associated with the electroweak interaction.
-
C.
weakerThan
Indicates that one entity has less strength, power, or effectiveness than another entity.
-
D.
interactsGravitationallyWith
Indicates that one entity exerts a gravitational influence on, and is influenced by, another entity, according to the laws of gravity.
-
E.
weakHypercharge
Indicates the value of a particle’s weak hypercharge, i.e., its charge under the U(1) component of the electroweak gauge symmetry that helps determine its electroweak interactions.
- 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc682d094819081a96ffb77c4c42a |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:49 p.m.