Triple
T3990700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Customs Court |
E86981
|
entity |
| Predicate | dateTransformedFromBoardOfGeneralAppraisers |
P10480
|
FINISHED |
| Object | 1926 |
—
|
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: 1926 | Statement: [United States Customs Court, dateTransformedFromBoardOfGeneralAppraisers, 1926]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateTransformedFromBoardOfGeneralAppraisers Context triple: [United States Customs Court, dateTransformedFromBoardOfGeneralAppraisers, 1926]
-
A.
reformDate
Indicates the date on which a reform, change, or restructuring officially took effect or was implemented.
-
B.
dateOfConversion
chosen
Indicates the specific date on which an entity changed status, form, or affiliation (e.g., religious, legal, or organizational conversion).
-
C.
dateApproximate
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
D.
dateRevisedTo
Indicates that an entity’s date has been updated or changed to a new specified date.
-
E.
dateObserved
Indicates the specific date on which an event, condition, or measurement was recorded or observed.
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.