Triple
T32552087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wendell Deaver |
E832001
|
entity |
| Predicate | homeTownInSeries |
P174586
|
FINISHED |
| Object | Boston, Massachusetts |
—
|
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: Boston, Massachusetts | Statement: [Wendell Deaver, homeTownInSeries, Boston, Massachusetts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTownInSeries Context triple: [Wendell Deaver, homeTownInSeries, Boston, Massachusetts]
-
A.
homeTownInUniverse
Indicates that a location is the character’s hometown within a specified fictional or defined universe.
-
B.
cityOfSeries
Indicates the city in which a series is primarily set, based, or associated.
-
C.
homeTownType
Indicates the type or classification of a person's hometown (e.g., city, village, suburb).
-
D.
homeCityInStory
Indicates that a specified city serves as a character’s home city within the context of a particular story.
-
E.
cityOfFictionalOrigin
Indicates the city from which a fictional character, entity, or work is described as originating within its narrative or fictional universe.
- F. None of above. chosen
Provenance (4 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5c7c66c8190a6895a998729fe69 |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c1b666188190ac43c3011a7df048 |
completed | May 3, 2026, 3:32 a.m. |
Created at: May 1, 2026, 1:02 a.m.