Triple
T18078830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Somerset |
E432629
|
entity |
| Predicate | involvedInFaction |
P106973
|
FINISHED |
| Object | Lancastrian faction |
—
|
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: Lancastrian faction | Statement: [Duke of Somerset, involvedInFaction, Lancastrian faction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedInFaction Context triple: [Duke of Somerset, involvedInFaction, Lancastrian faction]
-
A.
foughtForFaction
Indicates that an entity actively participated in or supported a particular faction, typically in a conflict or struggle.
-
B.
factionInvolved
Indicates that a particular faction participates in, is associated with, or plays a role in the specified event, situation, or context.
-
C.
factionAssociated
chosen
Indicates that an entity is connected to, aligned with, or belongs to a particular faction.
-
D.
hasFaction
Indicates that an entity is affiliated with, belongs to, or is represented by a particular faction or group.
-
E.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
- 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_69d8b9070cac81909fa9473fb1c3f1c7 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4d9f6a85481909894c39c8be98d5d |
completed | April 19, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:27 a.m.