Triple
T4537296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | matrix mechanics |
E107437
|
entity |
| Predicate | developedInYear |
P3297
|
FINISHED |
| Object | 1925 |
—
|
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: 1925 | Statement: [matrix mechanics, developedInYear, 1925]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedInYear Context triple: [matrix mechanics, developedInYear, 1925]
-
A.
developedSince
Indicates that something has been created, expanded, or advanced starting from a specified point in time and continuing thereafter.
-
B.
developedAt
Indicates the place or location where something was created, built, or developed.
-
C.
introducedInYear
chosen
Indicates the year in which something was first introduced, launched, or made available.
-
D.
developedWithin
Indicates that something was created, produced, or brought into existence inside a specified context, boundary, or time frame.
-
E.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
- 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_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. |
Created at: March 20, 2026, 1:04 p.m.