Triple
T18969133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Othon Friesz |
E464119
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Friesz |
—
|
NE NERFINISHED |
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: Friesz | Statement: [Othon Friesz, familyName, Friesz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Friesz Context triple: [Othon Friesz, familyName, Friesz]
-
A.
Friesz
chosen
Friesz is a surname most notably associated with the French Fauvist painter Othon Friesz.
-
B.
Fajsz
Fajsz was a 10th-century Grand Prince of the early Hungarian state, known primarily from medieval chronicles as one of the Árpád dynasty rulers.
-
C.
Feszl
Feszl is a Hungarian surname most notably associated with architect Frigyes Feszl, known for his contributions to 19th-century Hungarian architecture.
-
D.
Frieder
Frieder is a surname most notably associated with Bill Frieder, an American college basketball coach who led successful programs at the University of Michigan and Arizona State University.
-
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 (2 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d618e2ec8190848a41733e6db2f1 |
completed | April 20, 2026, 7:30 a.m. |
Created at: April 10, 2026, noon