Triple
T27134703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count of Wisborg |
E681650
|
entity |
| Predicate | titleHolderLoses |
P181406
|
FINISHED |
| Object | Swedish royal succession rights |
—
|
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: Swedish royal succession rights | Statement: [Count of Wisborg, titleHolderLoses, Swedish royal succession rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderLoses Context triple: [Count of Wisborg, titleHolderLoses, Swedish royal succession rights]
-
A.
titleHolderWas
Indicates that an entity previously held a specific title or position before it passed to someone or something else.
-
B.
titleHolderDuring
Indicates that one entity holds a specific title or position during a defined time period in relation to another entity.
-
C.
titleHolderIs
Indicates that one entity currently holds or possesses a specific title associated with another entity.
-
D.
titleHolderCouldBe
Indicates that a particular entity is a possible or potential holder of a specified title or position.
-
E.
titleHolderRetains
Indicates that the current title holder successfully keeps their title rather than losing or relinquishing it.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69f77648979c8190b6cdbb835ab8987c |
completed | May 3, 2026, 4:22 p.m. |
Created at: April 27, 2026, 9:06 a.m.