Triple
T7550762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | von Fock |
E178525
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Fock |
E178525
|
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: Fock | Statement: [von Fock, hasFamilyName, Fock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fock Context triple: [von Fock, hasFamilyName, Fock]
-
A.
Fock
chosen
Fock is a Swedish surname associated with several notable historical figures and families in Sweden.
-
B.
Fuchs
Fuchs is a German surname borne by numerous notable individuals across fields such as science, politics, and the arts.
-
C.
Focks
Focks is a variant or stylized form of the fox, typically referring to a creative, fictional, or branded reinterpretation of the animal.
-
D.
Fuhse
Fuhse is a river in Lower Saxony, Germany, that flows through several towns before joining the Aller River.
-
E.
Fiser
Fiser is a surname variant of Fischer, commonly associated with Central or Eastern European origins.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8b50e5c8190817c1e968294d1ad |
completed | March 27, 2026, 9:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c89a834d4c8190acf521fcff884109 |
completed | March 29, 2026, 3:20 a.m. |
Created at: March 27, 2026, 3:49 p.m.