Triple
T8524192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G. Albert Lansburgh |
E201770
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Gustave |
E55832
|
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: Gustave | Statement: [G. Albert Lansburgh, givenName, Gustave]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gustave Context triple: [G. Albert Lansburgh, givenName, Gustave]
-
A.
Gustave
chosen
Gustave is a masculine given name of French origin, famously borne by engineer Gustave Eiffel.
-
B.
Eugène
Eugène is a masculine given name of French origin, derived from the Greek "Eugenios," meaning "well-born" or "noble."
-
C.
Pierre
Pierre is a masculine given name of French origin that has been borne by numerous notable figures in history, arts, and science.
-
D.
René
René is a French given name commonly used for males and historically associated with several notable figures in politics, arts, and philosophy.
-
E.
Adolphe
Adolphe is the given name of Jean-Charles Adolphe Alphand, a prominent 19th-century French engineer known for designing many of Paris’s parks and boulevards.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe64362c88190b978a2544eec6e3e |
completed | March 31, 2026, 3:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cebb6855ec8190a85e5afeb656ee7d |
completed | April 2, 2026, 6:54 p.m. |
Created at: March 30, 2026, 6:16 p.m.