Triple
T30684234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry Clifford, 1st Earl of Cumberland |
E781139
|
entity |
| Predicate | reignOrServiceUnder |
P113707
|
FINISHED |
| Object | Tudor dynasty |
—
|
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: Tudor dynasty | Statement: [Henry Clifford, 1st Earl of Cumberland, reignOrServiceUnder, Tudor dynasty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reignOrServiceUnder Context triple: [Henry Clifford, 1st Earl of Cumberland, reignOrServiceUnder, Tudor dynasty]
-
A.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
-
B.
reignedUnder
chosen
Indicates that one entity exercised ruling authority or governance while being subordinate to, or under the higher sovereignty of, another entity.
-
C.
reignSupportedBy
Indicates that a ruler’s period of rule is backed, upheld, or sustained by a particular person, group, or power.
-
D.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
-
E.
reignAfter
Indicates that one entity begins its reign or rule following the conclusion of another entity's reign.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 8:33 p.m.