Triple
T21475661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancastrian forces |
E529853
|
entity |
| Predicate | statusAfter1485 |
P144502
|
FINISHED |
| Object | absorbed into royal forces of the Tudor monarchy |
—
|
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: absorbed into royal forces of the Tudor monarchy | Statement: [Lancastrian forces, statusAfter1485, absorbed into royal forces of the Tudor monarchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusAfter1485 Context triple: [Lancastrian forces, statusAfter1485, absorbed into royal forces of the Tudor monarchy]
-
A.
statusAfter1569
Indicates the status or condition an entity has after the year 1569, typically contrasting it with its prior status.
-
B.
statusAfter1806
Indicates the status or condition of an entity specifically in the period following the year 1806.
-
C.
statusAfter1970
Indicates the status or condition of an entity as it exists after the year 1970.
-
D.
statusAfter1627
Indicates the condition or state of an entity as it exists after the year 1627.
-
E.
statusAfter1995
Indicates the condition or state of an entity specifically in the period after the year 1995.
- F. None of above. chosen
Provenance (4 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_69e0c459acb481909bb6ee452a0045c7 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1737f881908ef7889e9568a4d3 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:19 p.m.