Triple
T22937221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfred, Duke of Saxe-Coburg and Gotha |
E569618
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Albert |
—
|
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: Albert | Statement: [Alfred, Duke of Saxe-Coburg and Gotha, givenName, Albert]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Albert Context triple: [Alfred, Duke of Saxe-Coburg and Gotha, givenName, Albert]
-
A.
Albert
Albert is the given name of Albert Leornes Greene, better known as the American soul singer Al Green.
-
B.
Albert
Albert was the first Duke of Prussia, a 16th-century ruler known for secularizing the Teutonic Order’s Prussian lands into a hereditary duchy under Polish suzerainty.
-
C.
Albert
Albert is a rational, steady, and respectable foil to Werther’s passionate temperament in Goethe’s novel "The Sorrows of Young Werther."
-
D.
Albert
chosen
Albert was the given name of Prince Albert of Prussia, a 19th-century Prussian royal and military figure from the House of Hohenzollern.
-
E.
Albert
Albert is a small rural locality within Lachlan Shire in New South Wales, Australia.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1813608e48190922df7a5386dc391 |
completed | April 29, 2026, 3:55 a.m. |
Created at: April 17, 2026, 3:45 p.m.