Triple
T23080490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lipschitz |
E575454
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Lipschitzh |
—
|
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: Lipschitzh | Statement: [Lipschitz, hasVariant, Lipschitzh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lipschitzh Context triple: [Lipschitz, hasVariant, Lipschitzh]
-
A.
Lipschitz
chosen
Lipschitz is a German surname most notably associated with mathematician Rudolf Lipschitz, whose name appears in concepts such as Lipschitz continuity in analysis.
-
B.
Lipschitz continuity condition
The Lipschitz continuity condition is a mathematical regularity criterion that bounds how fast a function can change, ensuring controlled variation and playing a key role in analysis and differential equations.
-
C.
LIPZ
LIPZ is the ICAO airport code for Venice Marco Polo Airport, the main international airport serving Venice, Italy.
-
D.
LIPK
LIPK is the ICAO airport code for Forlì International Airport in Forlì, Italy.
-
E.
LIP
LIP is the vehicle registration code for the town of Blomberg in the Lippe district of North Rhine-Westphalia, Germany.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e245be28d48190ad1348d5a73db37d |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18c66a80481909ebc2ba69f1e4bd9 |
completed | April 29, 2026, 4:43 a.m. |
Created at: April 17, 2026, 3:56 p.m.