Triple
T20148014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | maken–machen isogloss |
E491357
|
entity |
| Predicate | contrastsForm |
P138854
|
FINISHED |
| Object | "maken" |
—
|
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: "maken" | Statement: [maken–machen isogloss, contrastsForm, "maken"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contrastsForm Context triple: [maken–machen isogloss, contrastsForm, "maken"]
-
A.
contrastsState
Indicates a relationship where one state is presented as differing from or opposing another state, highlighting their contrast.
-
B.
providesContrastWith
Indicates that one entity is used to highlight differences or distinctions when compared with another entity.
-
C.
formsIn
Indicates that one entity takes shape, develops, or comes into existence within or inside another entity.
-
D.
registerContrast
Indicates that an entity records or establishes a distinction or difference between two or more items or states.
-
E.
initiallyContrastsWith
Indicates that one entity is first presented or perceived in opposition or contrast to another entity at the beginning of a sequence, process, or context.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667a0075c8190a5c4de53a0caa7f6 |
completed | April 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:33 p.m.