Triple
T192761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Z boson |
E3755
|
entity |
| Predicate | cParity |
P3975
|
FINISHED |
| Object | -1 |
—
|
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: -1 | Statement: [Z boson, cParity, -1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cParity Context triple: [Z boson, cParity, -1]
-
A.
hasParity
Indicates that two entities share the same parity property (e.g., both even or both odd) with respect to a specified attribute or value.
-
B.
hasChargeConjugation
chosen
Indicates that one entity is the charge-conjugated counterpart (particle vs. antiparticle form) of another entity.
-
C.
parallels
Indicates that one entity runs alongside or corresponds to another in a way that maintains a consistent separation or similarity without intersecting.
-
D.
crossType
Indicates a relationship where one entity intersects, passes over, or traverses another, typically implying movement or extension across a boundary, area, or medium.
-
E.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a259669ba08190a5be1d2e10e70b27 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a2567567508190b3a41329a15c7156 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.