Triple
T13564215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brigid Blake |
E323989
|
entity |
| Predicate | relationshipToSetting |
P44691
|
FINISHED |
| Object | host of Thanksgiving gathering |
—
|
LITERAL FINISHED |
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: host of Thanksgiving gathering | Statement: [Brigid Blake, relationshipToSetting, host of Thanksgiving gathering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToSetting Context triple: [Brigid Blake, relationshipToSetting, host of Thanksgiving gathering]
-
A.
associatedWithSetting
chosen
Indicates that one entity is connected or linked to a particular context, environment, or setting in which it occurs or is relevant.
-
B.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
relationshipType
Indicates the specific kind of relationship that exists between two or more entities.
-
D.
relationshipToHumans
Indicates the nature or type of connection, association, or relevance that something has specifically with humans.
-
E.
relationshipToChildren
Indicates the type of familial or social connection an entity has to one or more children.
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb00bbe848190bb33efe2af528295 |
completed | April 12, 2026, 2:45 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:47 p.m.