Triple
T226310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Secret Service |
E4320
|
entity |
| Predicate | transferEffectiveDate |
P4158
|
FINISHED |
| Object | 2003-03-01 |
—
|
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: 2003-03-01 | Statement: [United States Secret Service, transferEffectiveDate, 2003-03-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferEffectiveDate Context triple: [United States Secret Service, transferEffectiveDate, 2003-03-01]
-
A.
replacedCurrencyDate
Indicates the date on which one currency was officially replaced by another.
-
B.
movementDate
chosen
Indicates the date on which a movement, transfer, or relocation event occurs.
-
C.
integrationDate
Indicates the date on which two or more entities, systems, or components are combined or brought into a unified whole.
-
D.
surrenderDate
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
E.
nonCashEuroChangeoverDate
Indicates the date on which the transition to the euro occurred for non-cash transactions (such as accounting and electronic payments).
- 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_69a257363ffc81909757bde7ab3404da |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dec53ac8190912f3d79576131fa |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b5739dc8190bad8bfa330ce0499 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.