Triple
T34565886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grover's Corners |
E887480
|
entity |
| Predicate | hasCharacterLivingIn |
P168038
|
FINISHED |
| Object | George Gibbs |
—
|
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: George Gibbs | Statement: [Grover's Corners, hasCharacterLivingIn, George Gibbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterLivingIn Context triple: [Grover's Corners, hasCharacterLivingIn, George Gibbs]
-
A.
hasNotableResidentInFiction
Indicates that a place or entity is notably associated with a fictional character who is depicted as residing there.
-
B.
characterBasedIn
chosen
Indicates that a fictional character is primarily located, resides, or operates in a particular place or setting.
-
C.
hasMainCharacterFrom
Indicates that a work of fiction has a main character who originates from or belongs to a specified place, group, or source.
-
D.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
-
E.
inhabitedBy
Indicates that a place or location is lived in or occupied by a particular individual, group, or species.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 1, 2026, 2:02 a.m.