Triple
T21963653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Sweden |
E542401
|
entity |
| Predicate | titleHoldersMayAlsoHold |
P115009
|
FINISHED |
| Object | Duke of a Swedish province |
—
|
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: Duke of a Swedish province | Statement: [Prince of Sweden, titleHoldersMayAlsoHold, Duke of a Swedish province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHoldersMayAlsoHold Context triple: [Prince of Sweden, titleHoldersMayAlsoHold, Duke of a Swedish province]
-
A.
titleHoldersWere
Indicates that certain entities previously held a specified title or position during a past period.
-
B.
titleHoldersCollectively
Indicates that a group of entities jointly hold, share, or possess a particular title or set of titles as a collective.
-
C.
titleHolders
Indicates that one or more entities currently or formerly hold a specified title, position, or honor.
-
D.
titleHolderCouldBe
chosen
Indicates that a particular entity is a possible or potential holder of a specified title or position.
-
E.
titleHeldConcurrentlyWith
Indicates that one title or position was held at the same time as another title or position by the same 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12458e4488190a04f8d3958854b49 |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8:01 p.m.