Triple
T31546160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Mechanism |
E804877
|
entity |
| Predicate | adoptionDateOfEstablishingResolution |
P3399
|
FINISHED |
| Object | 2010-12-22 |
—
|
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: 2010-12-22 | Statement: [the Mechanism, adoptionDateOfEstablishingResolution, 2010-12-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptionDateOfEstablishingResolution Context triple: [the Mechanism, adoptionDateOfEstablishingResolution, 2010-12-22]
-
A.
dateAdopted
chosen
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
-
B.
decisionAdoptedAt
Indicates that a decision was formally adopted or approved at a specific time or event.
-
C.
presidentialAssentDate
Indicates the date on which a president formally gives assent or approval to a law, decision, or official act.
-
D.
dateOfFirstStatuteApproval
Indicates the date on which a statute (or legal act) was first formally approved.
-
E.
ratifiedAt
Indicates the date, time, or event context at which an agreement, treaty, or formal decision was officially ratified.
- 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_69f348d11a048190a65eb8384a3754ac |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 30, 2026, 10:08 p.m.