Triple
T10464810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dacre family |
E246762
|
entity |
| Predicate | loyaltyShifted |
P91356
|
FINISHED |
| Object | between rival factions during the Wars of the Roses |
—
|
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: between rival factions during the Wars of the Roses | Statement: [Dacre family, loyaltyShifted, between rival factions during the Wars of the Roses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loyaltyShifted Context triple: [Dacre family, loyaltyShifted, between rival factions during the Wars of the Roses]
-
A.
loyaltyChange
chosen
Indicates a change in the degree or direction of loyalty from one entity toward another over time.
-
B.
loyaltyDimension
Indicates the degree or aspect of loyalty characterizing the relationship between entities.
-
C.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
-
D.
loyaltySymbolizedBy
Indicates that an instance of loyalty is represented or expressed by a particular symbol or emblem.
-
E.
loyaltyMechanism
Indicates a mechanism or process through which loyalty is established, maintained, or reinforced between entities.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d50886c2a8819086da6c08356ec6bf |
completed | April 7, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:19 p.m.