Triple
T136845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seal of the United States Department of the Treasury |
E2764
|
entity |
| Predicate | dateReferenced |
P830
|
FINISHED |
| Object | 1789 |
—
|
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: 1789 | Statement: [Seal of the United States Department of the Treasury, dateReferenced, 1789]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateReferenced Context triple: [Seal of the United States Department of the Treasury, dateReferenced, 1789]
-
A.
date
Indicates that two entities are engaged in or participate in a romantic or social outing or relationship with each other.
-
B.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
dateOfRelatedEvent
chosen
Indicates that there is a specific date on which a related event associated with the subject occurs or occurred.
-
E.
acquisitionDate
Indicates the date on which one entity formally acquires or takes ownership of 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a4edf081908c494c8370c76b9a |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25652efdc8190b85b33735a9e6370 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.