Triple
T396601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Seal of the United States |
E8995
|
entity |
| Predicate | designCompletedOn |
P2286
|
FINISHED |
| Object | 1782-06-20 |
—
|
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: 1782-06-20 | Statement: [Great Seal of the United States, designCompletedOn, 1782-06-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designCompletedOn Context triple: [Great Seal of the United States, designCompletedOn, 1782-06-20]
-
A.
designDate
chosen
Indicates the date on which something was originally designed or its design was completed.
-
B.
commissionedAt
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
-
C.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
D.
constructionCompleted
Indicates that a construction process or project has been fully finished and reached its completed state.
-
E.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec8a941081909a152fda0ce24a98 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96d17d08190878d3a68b17d51ca |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.