Triple
T12105929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denise Lind |
E288303
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Lind |
E955391
|
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: Lind | Statement: [Denise Lind, familyName, Lind]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lind Context triple: [Denise Lind, familyName, Lind]
-
A.
Lind
chosen
Lind is a surname of German and Scandinavian origin borne by various notable individuals across fields such as the arts, politics, and academia.
-
B.
Linder
Linder is a river in Bavaria, Germany, known as a headwater stream of the Ammer that flows through the Ammergau Alps.
-
C.
Linder
Linder is a surname of likely European origin borne by various individuals and families.
-
D.
Lindberg
Lindberg is a small municipality in the Regen district of Bavaria, Germany, known for its location in the Bavarian Forest region.
-
E.
Lundie
Lundie is a small rural settlement in Angus, Scotland, situated near the Sidlaw Hills and known for its scenic countryside setting.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91561eaec819096ba00682d81f41a |
completed | April 10, 2026, 3:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f6795bf88190891acf918a432bef |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:49 p.m.