Triple
T25883939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vassall family |
E652126
|
entity |
| Predicate | fateOfManyMembers |
P33525
|
FINISHED |
| Object | exile to Britain |
—
|
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: exile to Britain | Statement: [Vassall family, fateOfManyMembers, exile to Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fateOfManyMembers Context triple: [Vassall family, fateOfManyMembers, exile to Britain]
-
A.
fateOfMembers
chosen
Indicates the outcome, destiny, or final status experienced by the members of a group or collection.
-
B.
manyMembersAre
Indicates that a large number of members within a group possess a specified property or participate in a particular role or condition.
-
C.
familyFate
Indicates a relationship where the outcome, destiny, or ultimate circumstances of one entity are determined by or closely tied to those of its family or familial group.
-
D.
includesMortalMember
Indicates that a group, category, or collection has at least one member that is mortal.
-
E.
multiMember
Indicates that an entity participates as a member in more than one group, collection, or organizational unit simultaneously.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f60340e45c819088e093e535e70022 |
completed | May 2, 2026, 1:59 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:17 a.m.