Triple
T37804544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clementine |
E942465
|
entity |
| Predicate | homeLocationPreApocalypse |
P91611
|
FINISHED |
| Object | Atlanta, Georgia |
—
|
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: Atlanta, Georgia | Statement: [Clementine, homeLocationPreApocalypse, Atlanta, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeLocationPreApocalypse Context triple: [Clementine, homeLocationPreApocalypse, Atlanta, Georgia]
-
A.
homeLocationInStory
Indicates the place that serves as a character’s primary home or base of residence within the context of the story.
-
B.
finalPreWarLocation
Indicates the last known location of an entity immediately before the onset of a specified war or conflict.
-
C.
homeCityInBackstory
chosen
Indicates that an entity has a specified city as its home city within its narrative or character backstory.
-
D.
residenceBeforeAttacks
Indicates that an entity’s place of residence is specified for the period prior to a particular attack or set of attacks.
-
E.
homeLocationInCoverIdentity
Indicates that an entity’s home location is specified within the context of its cover (false or assumed) identity.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.