Triple
T33650387
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Forz family |
E862081
|
entity |
| Predicate | heldContinentalLordship |
P28640
|
FINISHED |
| Object | County of Aumale |
—
|
NE NERFINISHED |
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: County of Aumale | Statement: [de Forz family, heldContinentalLordship, County of Aumale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldContinentalLordship Context triple: [de Forz family, heldContinentalLordship, County of Aumale]
-
A.
lastRulerWithFullContinentalHoldings
Indicates that the subject was the final ruler to maintain complete political control over the entire specified continent.
-
B.
heldEarldom
Indicates that a person possessed and held the noble title and rank of an earl.
-
C.
heldFief
Indicates that one entity possessed or controlled a fief (a feudal estate or tenure) from another entity.
-
D.
heldTerritory
chosen
Indicates that one entity maintained control or possession over a specific territory or geographic area.
-
E.
borderLord
Indicates that one entity serves as the feudal or territorial lord presiding over a border or frontier region associated with another entity.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.