Triple
T2540851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Continental Association |
E56379
|
entity |
| Predicate | plannedStartDateOfNonExportation |
P288
|
FINISHED |
| Object | 1775-09-10 |
—
|
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: 1775-09-10 | Statement: [Continental Association, plannedStartDateOfNonExportation, 1775-09-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedStartDateOfNonExportation Context triple: [Continental Association, plannedStartDateOfNonExportation, 1775-09-10]
-
A.
datePlanned
Indicates that a specific date has been scheduled or intended for a particular event, action, or relationship to occur.
-
B.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
-
C.
arrivalDatePlanned
Indicates the date on which an arrival is scheduled or expected to occur according to a plan.
-
D.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
E.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
- 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_69ab4a49b6508190bc467fbef4bac334 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd64a2194819097c66cbeb37fe859 |
completed | March 7, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69abd0c4a5dc819097812db50443420a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.