Triple
T19577456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West New Jersey |
E489894
|
entity |
| Predicate | dateOfConcessionsAndAgreements |
P2503
|
FINISHED |
| Object | 1677 |
—
|
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: 1677 | Statement: [West New Jersey, dateOfConcessionsAndAgreements, 1677]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfConcessionsAndAgreements Context triple: [West New Jersey, dateOfConcessionsAndAgreements, 1677]
-
A.
agreedAt
Indicates the time or point at which an agreement or consensus between parties was reached.
-
B.
treatyDate
chosen
Indicates the calendar date on which a treaty is formally agreed upon, signed, or comes into effect between parties.
-
C.
agreementSignedAt
Indicates the specific time and/or place at which an agreement was formally signed.
-
D.
dateGranted
Indicates the specific date on which a right, status, or permission was formally conferred or approved.
-
E.
treatyConcludedAfter
Indicates that one treaty was formally concluded at a later time than another specified treaty.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e64025d5d081909dbb0c079d366006 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.