Triple
T17961468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cec Linder |
E449092
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Linder |
—
|
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: Linder | Statement: [Cec Linder, familyName, Linder]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Linder Context triple: [Cec Linder, familyName, Linder]
-
A.
Linder
Linder is a river in Bavaria, Germany, known as a headwater stream of the Ammer that flows through the Ammergau Alps.
-
B.
Linder
chosen
Linder is a surname of likely European origin borne by various individuals and families.
-
C.
Lind
Lind is a surname of German and Scandinavian origin borne by various notable individuals across fields such as the arts, politics, and academia.
-
D.
Lindertis
Lindertis is a Scottish estate historically associated with the Munro family, notably giving its name to the baronetcy held by Sir Hugh Munro.
-
E.
Lindinis
Lindinis is the Roman-era name for the town now known as Ilchester in Somerset, England, which served as an important settlement in Roman Britain.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b132cc10819088526a0b4b098d69 |
completed | April 19, 2026, 10:40 a.m. |
Created at: April 10, 2026, 10:22 a.m.