Triple
T13177325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adrienne Nesser |
E313130
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Nesser |
E313130
|
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: Nesser | Statement: [Adrienne Nesser, familyName, Nesser]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nesser Context triple: [Adrienne Nesser, familyName, Nesser]
-
A.
Nesser
chosen
Nesser is a surname most notably associated with Adrienne Nesser, who is married to Green Day frontman Billie Joe Armstrong.
-
B.
Voss
Voss is a municipality in western Norway known for its scenic landscapes, outdoor sports, and traditional cultural festivals.
-
C.
Voss
Voss is a German surname borne by various notable individuals across fields such as politics, arts, and sciences.
-
D.
Voss
Voss is a premium Norwegian bottled water brand known for its minimalist cylindrical glass bottles and upscale positioning.
-
E.
Gyllensten
Gyllensten is a Swedish surname most notably associated with Lars Gyllensten, a prominent author and former member of the Swedish Academy.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c322fdc8190b05f2287eba9dda6 |
completed | April 10, 2026, 11:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6f5ea93bc81908087326b3d043727 |
completed | May 3, 2026, 7:14 a.m. |
Created at: April 9, 2026, 9:14 p.m.