Triple
T38431301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurricane Mills, Tennessee |
E903807
|
entity |
| Predicate | namedResident |
P1092
|
FINISHED |
| Object | Loretta Lynn |
—
|
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: Loretta Lynn | Statement: [Hurricane Mills, Tennessee, namedResident, Loretta Lynn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedResident Context triple: [Hurricane Mills, Tennessee, namedResident, Loretta Lynn]
-
A.
aliasOfResident
Indicates that one entity is an alternative name or alias used for a resident entity.
-
B.
hasNotableResident
chosen
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
-
C.
namedAfterResidenceOf
Indicates that one entity is named after the place where another entity lives or has lived.
-
D.
coResident
Indicates that two or more entities live in the same residence or dwelling at the same time.
-
E.
hasTypicalResident
Indicates that an entity characteristically or commonly has a particular type of resident associated with it.
- F. None of above.
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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd82ed2a4c81908bd7797fbd2e3d08 |
completed | May 8, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fd814cc10481908e4f8123d35a5d0c |
completed | May 8, 2026, 6:23 a.m. |
Created at: May 3, 2026, 4:31 p.m.