Triple
T2321397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tau neutrino |
E51187
|
entity |
| Predicate | rightHandedComponent |
P38058
|
FINISHED |
| Object | not included in minimal Standard Model |
—
|
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: not included in minimal Standard Model | Statement: [tau neutrino, rightHandedComponent, not included in minimal Standard Model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rightHandedComponent Context triple: [tau neutrino, rightHandedComponent, not included in minimal Standard Model]
-
A.
handedness
Indicates the preference or dominance of one hand over the other in performing actions or tasks.
-
B.
heldRight
Indicates that one entity is being held on the right side of another entity.
-
C.
battingHand
Indicates the handedness a player uses when batting, such as right-handed, left-handed, or switch.
-
D.
hasRuku
Indicates that an entity performs, contains, or is associated with a ruku (the bowing posture/section) within a prayer or recitation structure.
-
E.
hadRight
Indicates that an entity possessed a legal or moral entitlement to perform an action, access something, or claim something in relation to another entity or situation.
- 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.