Triple
T1043494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Note |
E22521
|
entity |
| Predicate | circulationPeriodEnd |
P19627
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [United States Note, circulationPeriodEnd, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circulationPeriodEnd Context triple: [United States Note, circulationPeriodEnd, late 20th century]
-
A.
circulationPeriod
Indicates the length of time during which an item is allowed to be borrowed, used, or remain in active circulation before it must be returned, renewed, or retired.
-
B.
pegPeriodEnd
Indicates the date or point in time at which a pegged or fixed rate, value, or condition ceases to apply.
-
C.
typicalEndDate
chosen
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
D.
endDateOfEntries
Indicates the date on which the referenced entries conclude or are no longer valid.
-
E.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8475ab48190848388eea6448cb6 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.