Triple
T32284654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jane Edna Hunter |
E824791
|
entity |
| Predicate | mainResidenceDuringCareer |
P30978
|
FINISHED |
| Object | Cleveland, Ohio |
—
|
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: Cleveland, Ohio | Statement: [Jane Edna Hunter, mainResidenceDuringCareer, Cleveland, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainResidenceDuringCareer Context triple: [Jane Edna Hunter, mainResidenceDuringCareer, Cleveland, Ohio]
-
A.
residenceDuringCareer
chosen
Indicates the place where an individual lived for a significant period while pursuing their professional career.
-
B.
residenceDuringLife
Indicates that an entity lived or resided in a particular place during some period of its lifetime.
-
C.
residenceAfterCareer
Indicates the place where an individual lives or settles after the conclusion of their professional career.
-
D.
residenceInWork
Indicates that an entity’s place of residence is located within or at the same site as their place of work.
-
E.
residenceAssociatedWithOffice
Indicates a relationship where a residence is connected or linked to a particular office, such as being located at, attached to, or officially designated for that office.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcce457c819091b711d6cc66c980 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.