Triple
T23973859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenzsche Regel |
E604308
|
entity |
| Predicate | formuliertImJahr |
P13128
|
FINISHED |
| Object | 1834 |
—
|
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: 1834 | Statement: [Lenzsche Regel, formuliertImJahr, 1834]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formuliertImJahr Context triple: [Lenzsche Regel, formuliertImJahr, 1834]
-
A.
formulatedInYear
chosen
Indicates the specific calendar year in which something was originally created, devised, or formally established.
-
B.
formedInYear
Indicates the year in which an entity was originally established, created, or came into existence.
-
C.
statedInYear
Indicates that something was declared, expressed, or formally stated during a specific calendar year.
-
D.
yearFormalized
Indicates the specific year in which the relationship, concept, or entity was officially established, recognized, or formalized.
-
E.
definedInYear
Indicates that something (such as an entity, concept, or item) was formally established, specified, or created in a particular calendar year.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1dda91c8190af716bceb3225aee |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:26 p.m.