Triple
T21961754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Lanman |
E542346
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Lanman |
—
|
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: Lanman | Statement: [James Lanman, familyName, Lanman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lanman Context triple: [James Lanman, familyName, Lanman]
-
A.
Lanman
chosen
Lanman is a surname most notably associated with American philanthropist William K. Lanman Jr., a major benefactor of Yale University.
-
B.
Lanier
Lanier is a surname most notably associated with Willie Lanier, a Hall of Fame American football linebacker.
-
C.
Puttnam
Puttnam is a surname most notably associated with British film producer and politician David Puttnam.
-
D.
Leeman
Leeman is the namesake of Leeman-Turner Arena at Grace Hall, likely a person honored for significant contributions to the associated institution or community.
-
E.
Leeman
Leeman is a small coastal town in the Mid West region of Western Australia, known for its fishing and relaxed seaside lifestyle.
- 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f124572738819098cc669aafa53cc6 |
completed | April 28, 2026, 9:19 p.m. |
Created at: April 16, 2026, 8 p.m.