Triple
T11936408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenny Holzer |
E284056
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Holzer |
E284056
|
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: Holzer | Statement: [Jenny Holzer, hasFamilyName, Holzer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Holzer Context triple: [Jenny Holzer, hasFamilyName, Holzer]
-
A.
Holzer
chosen
Holzer is the surname of Jenny Holzer, an American conceptual artist renowned for her text-based public art installations and provocative use of language.
-
B.
Kestenholz
Kestenholz is a municipality in the canton of Solothurn in Switzerland, located in the Gäu district.
-
C.
Riedholz
Riedholz is a small Swiss municipality located in the canton of Solothurn.
-
D.
Eyholz
Eyholz is a small settlement in the canton of Valais in southwestern Switzerland, situated near the town of Visp in the upper Rhône valley.
-
E.
Holzlar
Holzlar is a district of Bonn in the borough of Beuel, known for its residential character and proximity to natural areas such as the Ennert forest.
- 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903094218819092e11b273d87de65 |
completed | April 10, 2026, 2:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f4408d497c8190b051225140125e1f |
completed | May 1, 2026, 5:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.