Triple
T5735858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annapolis Convention of 1786 |
E126499
|
entity |
| Predicate | recommendedDate |
P65519
|
FINISHED |
| Object | second Monday in May 1787 |
—
|
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: second Monday in May 1787 | Statement: [Annapolis Convention of 1786, recommendedDate, second Monday in May 1787]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recommendedDate Context triple: [Annapolis Convention of 1786, recommendedDate, second Monday in May 1787]
-
A.
proposalDate
Indicates the date on which a proposal is formally made or submitted from one entity to another.
-
B.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
-
C.
approvalDate
Indicates the date on which an action, request, or item was formally approved.
-
D.
latestPossibleDate
Indicates the most recent date on which a given event, condition, or state can validly or feasibly occur.
-
E.
reenvisionedDate
Indicates the date on which something was newly reimagined, redesigned, or conceptually revised.
- F. None of above. chosen
Provenance (4 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c025596b5c81909b5626773c91cecb |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c022a50c048190aff24c63e7039dd6 |
completed | March 22, 2026, 5:11 p.m. |
Created at: March 22, 2026, 3:47 p.m.