Triple
T23255689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gustavus |
E581862
|
entity |
| Predicate | hasAnglicizedForm |
P3437
|
FINISHED |
| Object | Gustavus |
—
|
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: Gustavus | Statement: [Gustavus, hasAnglicizedForm, Gustavus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gustavus Context triple: [Gustavus, hasAnglicizedForm, Gustavus]
-
A.
Gustavus
chosen
Gustavus is a Latinized masculine given name historically borne by several Swedish kings and used in various European and English-speaking contexts.
-
B.
Saint Clair
Saint Clair is a Christian saint whose name has been given to various localities in France, reflecting his historical and religious significance.
-
C.
Saint Clair
Saint Clair is a small unincorporated community located in Hamblen County, Tennessee, United States.
-
D.
Struble
Struble is a surname most notably associated with Arthur Dewey Struble, a U.S. Navy admiral who played a key role in World War II and the Korean War.
-
E.
Muhlenberg
Muhlenberg is a German-origin surname notably associated with the influential American Muhlenberg family, including early political and religious leaders in the United States.
- 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193fadac881908579b5729718ee41 |
completed | April 29, 2026, 5:15 a.m. |
Created at: April 17, 2026, 4:11 p.m.