Triple
T38052630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ramon Berenguer II |
E949807
|
entity |
| Predicate | coReign |
P124083
|
FINISHED |
| Object | 1076–1082 |
—
|
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: 1076–1082 | Statement: [Ramon Berenguer II, coReign, 1076–1082]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coReign Context triple: [Ramon Berenguer II, coReign, 1076–1082]
-
A.
coReignStatus
Indicates that two or more entities share ruling authority simultaneously, such as jointly holding a throne or leadership position.
-
B.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
C.
reignWith
chosen
Indicates that one entity rules or holds sovereign authority jointly alongside another entity.
-
D.
reignIs
Indicates that one entity holds ruling authority or sovereignty over another for a specified period.
-
E.
underTheReignOf
Indicates that one entity existed or operated during the period when another entity (typically a ruler or authority) held power or governance.
- 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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.