Triple
T23973867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenzsche Regel |
E604308
|
entity |
| Predicate | ergänzt |
P55853
|
FINISHED |
| Object | Faradaysches Induktionsgesetz |
—
|
NE NERFINISHED |
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: Faradaysches Induktionsgesetz | Statement: [Lenzsche Regel, ergänzt, Faradaysches Induktionsgesetz]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ergänzt Context triple: [Lenzsche Regel, ergänzt, Faradaysches Induktionsgesetz]
-
A.
complement
Indicates that one entity completes, enhances, or makes another entity whole or more effective by providing what it lacks.
-
B.
enhancedBy
Indicates that one entity’s value, effectiveness, or impact is increased or improved as a result of another entity.
-
C.
designedToSupplement
Indicates that one entity is created or intended to enhance, complete, or add to the function, content, or effect of another entity.
-
D.
complements
Indicates that one entity enhances, completes, or improves another by providing qualities or functions that fit well together.
-
E.
laterComplementedBy
chosen
Indicates that an earlier entity is subsequently supplemented, enhanced, or completed by a later entity.
- 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.