Triple
T26571901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Importation of Persons Clause |
E666848
|
entity |
| Predicate | temporalRestrictionUntilYear |
P117678
|
FINISHED |
| Object | 1808 |
—
|
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: 1808 | Statement: [Importation of Persons Clause, temporalRestrictionUntilYear, 1808]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporalRestrictionUntilYear Context triple: [Importation of Persons Clause, temporalRestrictionUntilYear, 1808]
-
A.
cutOffDateYear
chosen
Indicates the calendar year that serves as the cutoff point beyond which something no longer applies, is valid, or is considered.
-
B.
endYear
Indicates the year in which an event, state, or relationship comes to an end.
-
C.
tookPlaceUntil
Indicates that an event or situation occurred continuously or repeatedly up to a specified end time or date, after which it no longer took place.
-
D.
optionalYearBefore
Indicates that one entity may, but does not necessarily, occur or be valid in a year that precedes the year associated with another entity.
-
E.
travelEndYear
Indicates the year in which a travel event or journey concludes.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614a519f0819087c98f8b48d14cce |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:58 a.m.