Triple
T2072319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maurice |
E44841
|
entity |
| Predicate | cognate |
P2527
|
FINISHED |
| Object | Moritz |
E176784
|
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: Moritz | Statement: [Maurice, cognate, Moritz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moritz Context triple: [Maurice, cognate, Moritz]
-
A.
Moritz
chosen
Moritz is a masculine given name of German origin, commonly used in German-speaking countries.
-
B.
Philipp Moritz
Philipp Moritz is a researcher in machine learning and reinforcement learning, known for co-authoring influential work such as the Proximal Policy Optimization (PPO) algorithm.
-
C.
Franz
Franz is the given name of Franz Cardinal König, a prominent 20th-century Austrian Catholic cardinal and influential church leader.
-
D.
Johann
Johann is a given name of Germanic origin commonly used in German-speaking and other European countries.
-
E.
Othmar
Othmar is a masculine given name of Germanic origin, notably borne by the Swiss-American civil engineer Othmar Ammann.
- 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_69a88916c2b48190a5ca2e9b12cad3ed |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba0eaa5081908f6d6ff80f79b1c9 |
completed | March 7, 2026, 5:39 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69af6533d4b88190ac722cd1ebfa3d8f |
completed | March 10, 2026, 12:26 a.m. |
Created at: March 4, 2026, 7:41 p.m.