Triple
T16868787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Voss |
E410113
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Voss |
E723667
|
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: Voss | Statement: [Philip Voss, hasFamilyName, Voss]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Voss Context triple: [Philip Voss, hasFamilyName, Voss]
-
A.
Voss
Voss is a municipality in western Norway known for its scenic landscapes, outdoor sports, and traditional cultural festivals.
-
B.
Voss
Voss is a premium Norwegian bottled water brand known for its minimalist cylindrical glass bottles and upscale positioning.
-
C.
Voss
chosen
Voss is a German surname borne by various notable individuals across fields such as politics, arts, and sciences.
-
D.
Fossum
Fossum is an archaeological site in Norway known for its Bronze Age rock carvings that form part of the Tanum World Heritage landscape.
-
E.
Finneran
Finneran is a surname most notably associated with former NFL wide receiver Brian Finneran.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b50a82348190b3e33fd558aa3c7f |
completed | April 18, 2026, 4:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c2aba8c481908f5ff1ddc4b255cb |
completed | May 10, 2026, 5:38 p.m. |
Created at: April 10, 2026, 5:24 a.m.