Triple
T37791716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RCh XIII |
E942102
|
entity |
| Predicate | monarchAsGrandMasterContext |
P49189
|
FINISHED |
| Object | King of Sweden |
—
|
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: King of Sweden | Statement: [RCh XIII, monarchAsGrandMasterContext, King of Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchAsGrandMasterContext Context triple: [RCh XIII, monarchAsGrandMasterContext, King of Sweden]
-
A.
monarchAsGrandMaster
chosen
Indicates that a monarch holds the position and authority of a grand master within an order or organization.
-
B.
monarchicContext
Indicates that the relationship or action occurs within, is shaped by, or pertains to a monarchical system of rule or authority.
-
C.
monarchUntil
Indicates that an entity served as monarch over another entity up to, but not beyond, a specified end time or event.
-
D.
grandMaster
Indicates that one entity holds the highest authoritative or mastery status over a domain, discipline, or organization in relation to another entity.
-
E.
monarchAtStart
Indicates that the referenced entity was the reigning monarch at the beginning of a specified period, event, or sequence.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.