Triple
T257482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colony of Rhode Island and Providence Plantations |
E5466
|
entity |
| Predicate | charterDate |
P8990
|
FINISHED |
| Object | 1663 |
—
|
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: 1663 | Statement: [Colony of Rhode Island and Providence Plantations, charterDate, 1663]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterDate Context triple: [Colony of Rhode Island and Providence Plantations, charterDate, 1663]
-
A.
designationDate
Indicates the date on which an entity is formally assigned, designated, or given a particular status or role.
-
B.
charteredIn
Indicates that an organization or entity has been formally established, authorized, or incorporated within a specified jurisdiction or location.
-
C.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
-
D.
treatyDate
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
E.
dateEnacted
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
- 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_69a2580a64ac8190ad76e34bb0715b5e |
completed | Feb. 28, 2026, 2:50 a.m. |
| NER | Named-entity recognition | batch_69a25d703e688190bb86c69527e306f5 |
completed | Feb. 28, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69a25b694c08819085bb4b256fa7736f |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c4b773c81908f1017f40b0bfd07 |
completed | Feb. 28, 2026, 3:08 a.m. |
Created at: Feb. 28, 2026, 2:55 a.m.