Triple
T23281405
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lyman L. Lemnitzer |
E588872
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Lyman |
—
|
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: Lyman | Statement: [Lyman L. Lemnitzer, givenName, Lyman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lyman Context triple: [Lyman L. Lemnitzer, givenName, Lyman]
-
A.
Lyman
Lyman is a small town located in Skagit County in the state of Washington, United States.
-
B.
Lyman
Lyman is a small town in South Carolina known historically for its textile mill roots and suburban residential character within the Spartanburg metropolitan area.
-
C.
Lyman
Lyman is a small village located in Scotts Bluff County in the western part of the U.S. state of Nebraska.
-
D.
Lyman
Lyman is a town in eastern Ukraine’s Donetsk Oblast, known as a regional railway hub and for its proximity to the Sviatohirsk (Svyatye Gory) area along the Siverskyi Donets River.
-
E.
Lyman
chosen
Lyman is a masculine given name of English origin that has been borne by various notable figures, including the American clergyman and reformer Lyman Beecher.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19643b8908190a2c29552b272dc61 |
completed | April 29, 2026, 5:25 a.m. |
Created at: April 17, 2026, 4:57 p.m.