Triple
T18621769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindsey Nelson |
E455168
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Lindsey |
—
|
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: Lindsey | Statement: [Lindsey Nelson, givenName, Lindsey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lindsey Context triple: [Lindsey Nelson, givenName, Lindsey]
-
A.
Lindsey
chosen
Lindsey is a given name commonly used in English-speaking countries for both females and males.
-
B.
Lindsey
Lindsey is a historic region in eastern England, traditionally forming the northern part of the county of Lincolnshire.
-
C.
Lindsay
Lindsay is a small agricultural city in Tulare County, California, known for its citrus production in the San Joaquin Valley.
-
D.
Lindsay
Lindsay is a surname most notably associated with American poet Vachel Lindsay, a key figure in early 20th-century performance and visionary poetry.
-
E.
Lindsay
Lindsay is a feminine given name of English origin, used both as a first name and a surname.
- 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_69d8d38cc7948190a55ea64e5638994e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54f0146f48190a872032db6e660c6 |
completed | April 19, 2026, 9:54 p.m. |
Created at: April 10, 2026, 11:46 a.m.