Triple
T2235546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucy Flucker Knox |
E49270
|
entity |
| Predicate | familyPoliticalAlignment |
P16609
|
FINISHED |
| Object | Loyalist |
—
|
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: Loyalist | Statement: [Lucy Flucker Knox, familyPoliticalAlignment, Loyalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: familyPoliticalAlignment Context triple: [Lucy Flucker Knox, familyPoliticalAlignment, Loyalist]
-
A.
traditionalPoliticalAlignment
Indicates how closely an entity’s political views or affiliations align with established, historically dominant, or customary political positions within a given context.
-
B.
politicalIdentity
chosen
Indicates the political affiliation, ideology, or stance that characterizes an entity’s position within a political spectrum or system.
-
C.
politicalBase
Indicates the primary group, region, or constituency that provides core political support or power for an individual or organization.
-
D.
politicalSide
Indicates the political alignment or ideological position that one entity holds in relation to political spectra or groupings.
-
E.
houseAffiliation
Indicates the association or belonging of an entity to a particular house or household.
- 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc093ba0c819091df09a0e018fce1 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.