Triple
T10053593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fischler reform |
E208807
|
entity |
| Predicate | legislativeAgreementDate |
P69481
|
FINISHED |
| Object | June 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: June 2003 | Statement: [Fischler reform, legislativeAgreementDate, June 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeAgreementDate Context triple: [Fischler reform, legislativeAgreementDate, June 2003]
-
A.
legislatedOn
Indicates that a legislative body has formally considered, debated, or enacted laws or regulations concerning a particular subject or entity.
-
B.
agreedAt
chosen
Indicates the time or point at which an agreement or consensus between parties was reached.
-
C.
ratifiedAt
Indicates the date, time, or event context at which an agreement, treaty, or formal decision was officially ratified.
-
D.
dateSignedIntoLaw
Indicates the date on which a law or legal measure was formally approved and enacted into law.
-
E.
ratifiedOn
Indicates the date or point in time at which an agreement, treaty, or formal decision was officially approved and made valid.
- 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_69ca836094408190a36a1ea7e9a86fcd |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf9241208190b38e5e7a1604589c |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:57 p.m.