Triple
T1638639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Francis II of France |
E35415
|
entity |
| Predicate | coMonarchRole |
P20618
|
FINISHED |
| Object | King consort of Scotland |
—
|
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: King consort of Scotland | Statement: [Francis II of France, coMonarchRole, King consort of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coMonarchRole Context triple: [Francis II of France, coMonarchRole, King consort of Scotland]
-
A.
coMonarch
chosen
Indicates a relationship where two or more individuals jointly hold the position and authority of monarch over the same realm or polity.
-
B.
monarchRole
Indicates that an entity holds or is assigned the role, office, or position of a monarch in relation to a state or domain.
-
C.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
D.
commonMonarchOf
Indicates that two or more entities share the same monarch as their head of state or ruling sovereign.
-
E.
refersToRole
Indicates that one entity designates, mentions, or points to another entity specifically in its capacity as a role or position.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.