Triple
T134979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Charter for Regional or Minority Languages |
E2728
|
entity |
| Predicate | enteredIntoForceDate |
P448
|
FINISHED |
| Object | 1998-03-01 |
—
|
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: 1998-03-01 | Statement: [European Charter for Regional or Minority Languages, enteredIntoForceDate, 1998-03-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredIntoForceDate Context triple: [European Charter for Regional or Minority Languages, enteredIntoForceDate, 1998-03-01]
-
A.
enteredIntoForce
chosen
Indicates that a law, treaty, agreement, or regulation has become legally effective and binding from a specific point in time.
-
B.
ordinationDate
Indicates the date on which an individual was formally ordained to a religious office or role.
-
C.
dateEnacted
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
-
D.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
E.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a3ad908190b6a8652f09ae0cbb |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25650251c81908a6ea6368cd61198 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.