Triple
T23973882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenzsche Regel |
E604308
|
entity |
| Predicate | istVerwandtMit |
P7844
|
FINISHED |
| Object | Rechter-Hand-Regel |
—
|
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: Rechter-Hand-Regel | Statement: [Lenzsche Regel, istVerwandtMit, Rechter-Hand-Regel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: istVerwandtMit Context triple: [Lenzsche Regel, istVerwandtMit, Rechter-Hand-Regel]
-
A.
heraldicRelationship
Indicates a relationship between entities expressed through heraldic symbolism, such as coats of arms, crests, or heraldic devices.
-
B.
hasFamilialTieTo
chosen
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
C.
associatedHeir
Indicates that one entity is designated or recognized as the heir connected to, or inheriting from, another entity.
-
D.
moreCloselyRelatedTo
Indicates that one entity has a stronger or closer relationship, connection, or similarity to a second entity than to some other reference entity.
-
E.
moreDistantlyRelatedTo
Indicates that one entity is related to another by a more distant or indirect relationship compared to some closer reference relationship.
- 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.