Triple
T5291413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian throne |
E119749
|
entity |
| Predicate | unionWithSwedenEnd |
P63340
|
FINISHED |
| Object | 1905 |
—
|
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: 1905 | Statement: [Norwegian throne, unionWithSwedenEnd, 1905]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionWithSwedenEnd Context triple: [Norwegian throne, unionWithSwedenEnd, 1905]
-
A.
northernPartAnnexedBy
Indicates that the northern portion of an entity has been taken over and incorporated into another entity.
-
B.
unificationDate
Indicates the date on which two or more previously separate entities were formally unified into a single entity.
-
C.
wasDividedByTreaty
Indicates that an entity (such as a territory or region) was partitioned or separated as the result of a formal treaty or agreement.
-
D.
endOfRuleOverGermanEmpire
Indicates the point in time or event at which the rule or governance of the German Empire comes to an end.
-
E.
MunichAgreementSignatory
Indicates that an entity was a formal signatory to the Munich Agreement.
- 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
| PDg | Predicate description generation | batch_69bd86800630819096dad2eb2248c372 |
completed | March 20, 2026, 5:40 p.m. |
Created at: March 20, 2026, 1:52 p.m.