Triple
T7549625
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contraband decision |
E178496
|
entity |
| Predicate | appliedInYear |
P61341
|
FINISHED |
| Object | 1861 |
—
|
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: 1861 | Statement: [Contraband decision, appliedInYear, 1861]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedInYear Context triple: [Contraband decision, appliedInYear, 1861]
-
A.
deploymentYear
Indicates the calendar year in which an entity (such as a system, product, or resource) was first put into active use or operation.
-
B.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
C.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
D.
foundInYear
chosen
Indicates the specific calendar year in which something was discovered, created, established, or otherwise found.
-
E.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
- 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_69c69f2cbe08819088f9eb0c03ef529b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8b35ba481908e1e5bbf329daa33 |
completed | March 27, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69c6f4daad6c8190af2b8ae88d2c8cb7 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:49 p.m.