Triple
T429517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article I of the United States Constitution |
E9681
|
entity |
| Predicate | wasAdoptedOn |
P3399
|
FINISHED |
| Object | June 21, 1788 |
—
|
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 21, 1788 | Statement: [Article I of the United States Constitution, wasAdoptedOn, June 21, 1788]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasAdoptedOn Context triple: [Article I of the United States Constitution, wasAdoptedOn, June 21, 1788]
-
A.
adoptedAt
Indicates the time or date at which an adoption event took place.
-
B.
officialAdoptionYear
Indicates the year in which something (such as a policy, standard, symbol, or practice) was formally adopted or officially put into use.
-
C.
dateAdopted
chosen
Indicates the date on which something (such as a policy, standard, or item) was formally accepted or put into official use.
-
D.
adoptedAfter
Indicates that one entity was adopted at a later time than another entity.
-
E.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
- 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2eeedf68c81908473d6c6600961bd |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd7a3608190b8785c7b7205f6c1 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.