Triple
T9589147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfred Adler |
E231371
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Adler |
E231371
|
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: Adler | Statement: [Alfred Adler, familyName, Adler]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adler Context triple: [Alfred Adler, familyName, Adler]
-
A.
Adler
chosen
Adler is a German surname most famously associated with Alfred Adler, the Austrian physician and founder of individual psychology.
-
B.
Adler
Adler is a resort district of Sochi on Russia’s Black Sea coast, known as a major transport hub and holiday destination.
-
C.
Adoian
Adoian is the original Armenian surname of the influential abstract expressionist painter Arshile Gorky.
-
D.
Sigmund
Sigmund is the given name of Sigmund Freud, the pioneering Austrian neurologist and founder of psychoanalysis.
-
E.
Adelbert
Adelbert is a masculine given name of German origin, historically borne by figures such as the poet and naturalist Adelbert von Chamisso.
- 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_69ca848161688190a68d514a0a9d5129 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd99f1696c8190addf1a43544f2c18 |
completed | April 1, 2026, 10:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d161880adc819090a9be75ba2a1642 |
completed | April 4, 2026, 7:07 p.m. |
Created at: March 30, 2026, 8:06 p.m.