Triple
T4537299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | matrix mechanics |
E107437
|
entity |
| Predicate | keyRelation |
P57924
|
FINISHED |
| Object | [q,p] = iħ |
—
|
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: [q,p] = iħ | Statement: [matrix mechanics, keyRelation, [q,p] = iħ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyRelation Context triple: [matrix mechanics, keyRelation, [q,p] = iħ]
-
A.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
B.
datumRelation
Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
-
C.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
D.
hasKeyRelationship
Indicates a relationship where one entity serves as a key (e.g., identifier, access token, or primary reference) that grants access to, controls, or uniquely identifies another entity.
-
E.
keyField
Indicates that the referenced field serves as a primary or unique identifier within a data structure or record.
- 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_69bd43f922788190b7edfa294e39b178 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd57b78b8481909d79131723d4be22 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b4a9508190acdb888eef18f1ee |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:04 p.m.