Triple
T21074271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louis Zukofsky |
E519190
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Louis |
—
|
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: Louis | Statement: [Louis Zukofsky, givenName, Louis]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Louis Context triple: [Louis Zukofsky, givenName, Louis]
-
A.
Louis
Louis is the friendly, trumpet-playing alligator who dreams of becoming a jazz musician in Disney's animated film "The Princess and the Frog."
-
B.
Louis
Louis is the family name of Spyridon Louis, the Greek runner who won the first modern Olympic marathon in 1896.
-
C.
Louis
Louis is the given first name of Lou Piniella, a former Major League Baseball outfielder and World Series–winning manager.
-
D.
Louis
chosen
Louis is the given name of Louis Bromfield, an American author and early environmental conservationist known for his novels and pioneering work in sustainable agriculture.
-
E.
Louis
Louis was the given name of Louis II, Duke of Bavaria, a medieval German nobleman and regional ruler.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702d5ae908190ab5303e39443d729 |
completed | April 21, 2026, 4:53 a.m. |
Created at: April 16, 2026, 2:48 p.m.