Triple
T19903438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard N. Haass |
E478351
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Haass |
—
|
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: Haass | Statement: [Richard N. Haass, familyName, Haass]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haass Context triple: [Richard N. Haass, familyName, Haass]
-
A.
Haass
chosen
Haass is a surname most notably associated with Richard N. Haass, an American diplomat and longtime president of the Council on Foreign Relations.
-
B.
Haasz
Haasz is a surname variant of Haas, typically of German or Ashkenazi Jewish origin.
-
C.
Haase
Haase is a surname of German origin commonly borne by individuals in German-speaking countries and their descendants.
-
D.
Ghirshman
Ghirshman is the surname of Roman Ghirshman, a prominent 20th-century French archaeologist known for his influential work on ancient Iran and the Near East.
-
E.
Konrad Haase
Konrad Haase was a German military officer who commanded defending forces during the World War II Dieppe Raid in 1942.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65944c55481909b54a8f9a9c087d6 |
completed | April 20, 2026, 4:50 p.m. |
Created at: April 10, 2026, 1:52 p.m.