Triple
T15098919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A. Lange & Söhne |
E360610
|
entity |
| Predicate | notableModel |
P1503
|
FINISHED |
| Object | Lange 1 |
E1136850
|
NE 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: Lange 1 | Statement: [A. Lange & Söhne, notableModel, Lange 1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lange 1 Context triple: [A. Lange & Söhne, notableModel, Lange 1]
-
A.
Lange 1
chosen
Lange 1 is A. Lange & Söhne’s iconic luxury wristwatch model, renowned for its off-center dial layout, large date display, and high-end German watchmaking craftsmanship.
-
B.
Lange
Lange is a German surname borne by numerous notable individuals across fields such as science, politics, arts, and sports.
-
C.
Longo
Longo is an Italian surname borne by various notable figures in politics, arts, and sports.
-
D.
Langer
Langer is a surname most notably associated with Robert Langer, a pioneering American chemical engineer and prolific inventor in biotechnology and drug delivery.
-
E.
Langebrug
Langebrug is a historic bridge spanning the Spaarne River in the Dutch city of Haarlem.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0054f00388190a5123d9f4a869b96 |
completed | April 15, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feb7e6fc7c8190b517a7daa567d67c |
completed | May 9, 2026, 4:28 a.m. |
Created at: April 10, 2026, 3:04 a.m.