Triple
T13388851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sascha Goc |
E319517
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Goc |
E1037276
|
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: Goc | Statement: [Sascha Goc, familyName, Goc]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goc Context triple: [Sascha Goc, familyName, Goc]
-
A.
Goc
chosen
Goc is a German surname most notably associated with professional ice hockey players such as Marcel Goc.
-
B.
GOC
GOC is the standardised set of spelling and writing rules used for modern Scottish Gaelic.
-
C.
Goh
Goh is a surname and given name commonly found in East and Southeast Asia, often representing a romanization of several different Chinese surnames.
-
D.
Gou
Gou is a Chinese surname most prominently associated with Terry Gou, the Taiwanese billionaire founder of Foxconn.
-
E.
GOS
GOS is the acronym for the Global Observing System, an international network of instruments and facilities that continuously monitor the Earth's atmosphere, oceans, and land for weather and climate services.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d3a40081909ba49556130ad0e7 |
completed | April 12, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7306df34c81909f2ad5b753b7fb7f |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:34 p.m.