Triple
T3882473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian Constitution Day |
E92856
|
entity |
| Predicate | significanceDate |
P925
|
FINISHED |
| Object | 1814 |
—
|
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: 1814 | Statement: [Norwegian Constitution Day, significanceDate, 1814]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significanceDate Context triple: [Norwegian Constitution Day, significanceDate, 1814]
-
A.
dateSignificance
Indicates the specific importance, meaning, or notable role that a particular date holds within a given context or relationship.
-
B.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
C.
notableOperationDate
Indicates the date on which a significant or noteworthy operation, event, or activity associated with an entity took place.
-
D.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
E.
designationDate
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee7574c408190893e70bf80514838 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.