Triple
T17243088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. E. Langer |
E418550
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Langer |
E44890
|
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: Langer | Statement: [R. E. Langer, familyName, Langer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langer Context triple: [R. E. Langer, familyName, Langer]
-
A.
Langer
chosen
Langer is a surname most notably associated with Robert Langer, a pioneering American chemical engineer and prolific inventor in biotechnology and drug delivery.
-
B.
Lange
Lange is a German surname borne by numerous notable individuals across fields such as science, politics, arts, and sports.
-
C.
Langhans
Langhans is a German surname most notably associated with Carl Gotthard Langhans, the architect of Berlin’s Brandenburg Gate.
-
D.
Lenglern
Lenglern is a village in Lower Saxony, Germany, that forms one of the districts of the municipality of Bovenden near Göttingen.
-
E.
Lennertz
Lennertz is a German-origin surname borne by various individuals, including American composer Christopher Lennertz.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e21003c81908c884a3c8712676a |
completed | April 19, 2026, 1:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0170f388608190b709b1c228a7ba29 |
completed | May 11, 2026, 6:02 a.m. |
Created at: April 10, 2026, 5:39 a.m.