Triple
T478410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S-matrix |
E9111
|
entity |
| Predicate | probabilityRelation |
P12745
|
FINISHED |
| Object | P_{i→f} = |S_{fi}|^2 |
—
|
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: P_{i→f} = |S_{fi}|^2 | Statement: [S-matrix, probabilityRelation, P_{i→f} = |S_{fi}|^2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: probabilityRelation
Context triple: [S-matrix, probabilityRelation, P_{i→f} = |S_{fi}|^2]
-
A.
definesProbability
chosen
Indicates that one entity specifies or assigns the probability value associated with another entity or event.
-
B.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
C.
datumRelation
Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
-
D.
temporalRelation
Indicates a relationship that specifies how two events or states are positioned relative to each other in time (e.g., before, after, or overlapping).
-
E.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
- 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f056459881909749764cc4a7f9e8 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf017548190ae38ff3314a1ffa3 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.