Triple
T7384295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karelian pies |
E170341
|
entity |
| Predicate | hasEURegistrationYear |
P76689
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Karelian pies, hasEURegistrationYear, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEURegistrationYear Context triple: [Karelian pies, hasEURegistrationYear, 2003]
-
A.
hasMemberInEEA
Indicates that an entity has at least one member who is located in, based in, or belongs to the European Economic Area (EEA).
-
B.
hasEuropeanUnionMembershipThrough
Indicates that an entity holds membership in the European Union indirectly or by virtue of another entity (such as a state, territory, or organization) through which that membership is conferred.
-
C.
isProEuropean
Indicates support for European integration, institutions, or policies, or a generally favorable stance toward the European Union.
-
D.
legalStatusInEuropeanUnion
Indicates the legal status or standing that an entity holds within the jurisdictional framework of the European Union.
-
E.
declaredYear
Indicates the year in which something was formally announced, established, or proclaimed.
- 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_69c68a5d0ed08190b6d361e68f813330 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1efe1308190b96eefbff56140be |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f02ee3e08190a7a00c981129b22c |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0ebf9c88190af5a4d87d3fd338a |
completed | March 27, 2026, 9:04 p.m. |
Created at: March 27, 2026, 3:08 p.m.