Triple
T23896934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystic Falls, Virginia |
E600928
|
entity |
| Predicate | filmingLocationDouble |
P31730
|
FINISHED |
| Object | Covington, 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: Covington, Georgia | Statement: [Mystic Falls, Virginia, filmingLocationDouble, Covington, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmingLocationDouble Context triple: [Mystic Falls, Virginia, filmingLocationDouble, Covington, Georgia]
-
A.
filmingLocationContext
Indicates the contextual relationship specifying where the filming of an event, scene, or production took place.
-
B.
filmingLocationPattern
Indicates the typical or recurring geographic pattern of locations where filming for a production takes place.
-
C.
notableFilmingLocation
chosen
Indicates that a place served as a significant or well-known location where a film or television production was shot.
-
D.
formerFilmingLocation
Indicates that a place was once used as a filming location for a work but is no longer used for that purpose.
-
E.
filmingLocationForAdaptation
Indicates the place where an adaptation (such as a film or TV version of a work) was shot or recorded.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdda39448190bdefa953e0558583 |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.