Triple
T29799461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rebecca |
E756651
|
entity |
| Predicate | settingReign |
P179232
|
FINISHED |
| Object | reign of Richard I of England |
—
|
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: reign of Richard I of England | Statement: [Rebecca, settingReign, reign of Richard I of England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingReign Context triple: [Rebecca, settingReign, reign of Richard I of England]
-
A.
settingMonarch
Indicates that one entity serves as the reigning monarch or sovereign ruler within the context or setting of another entity.
-
B.
reignStart
Indicates the date or point in time when an entity’s period of ruling or governing authority begins.
-
C.
reignWith
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
-
D.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
E.
reignAs
Indicates that an entity holds and exercises ruling authority or sovereignty over a domain or people for a period of time.
- 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_69f22454583081908927516cb9938d1d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 29, 2026, 5:17 p.m.