Triple
T23896925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mystic Falls, Virginia |
E600928
|
entity |
| Predicate | hasFoundingFamily |
P53996
|
FINISHED |
| Object | Salvatore family |
—
|
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: Salvatore family | Statement: [Mystic Falls, Virginia, hasFoundingFamily, Salvatore family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoundingFamily Context triple: [Mystic Falls, Virginia, hasFoundingFamily, Salvatore family]
-
A.
foundedByFamily
chosen
Indicates that an organization, institution, or entity was established by one or more members of the same family.
-
B.
hasFamilyBranch
Indicates that one entity is a subdivision, offshoot, or branch within the broader family group or lineage of another entity.
-
C.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
D.
hasCentralFamily
Indicates that an entity possesses or is organized around a primary or core family unit.
-
E.
heldByFamilySince
Indicates that something has been continuously possessed or owned by the same family from a certain point in time.
- 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.