Triple
T95284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W boson |
E1916
|
entity |
| Predicate | obeys |
P134
|
FINISHED |
| Object | Bose–Einstein statistics |
—
|
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: Bose–Einstein statistics | Statement: [W boson, obeys, Bose–Einstein statistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obeys Context triple: [W boson, obeys, Bose–Einstein statistics]
-
A.
subordinateTo
Indicates that one entity holds a lower rank, status, or authority and is subject to the control, direction, or oversight of another entity.
-
B.
follows
chosen
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
C.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
D.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
E.
affirms
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebb3da08190a8b82564f33cde3b |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.